You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the Nov 20 API WG discussion, we discussed that we may want to wait till remote resolution is stable before promoting this to stable.
One identified gap is that currently it records a snapshot of the feature flags used during execution. However, if the flag is modified mid way through pipeline execution, it will not be detected
e2e test usage example in Chains (where the invocation.configsource and invocation.environment in the provenance are populated with the value from the provenance field.)
The text was updated successfully, but these errors were encountered:
Feature looking for Promotion
The field provenance that was introduced as alpha in v0.41.0 and to beta in v0.48.0
Current Feature Version
beta
Raise Feature Version
stable
Pipeline Release
alpha: v0.41.0
beta: 0.48.0
Issues Reported by the Users
provenance
field in *Run status #6309Usage in Dogfooding Cluster
Examples/Tests
e2e test
usage example in Chains (where the invocation.configsource and invocation.environment in the provenance are populated with the value from the provenance field.)
The text was updated successfully, but these errors were encountered: