-
Notifications
You must be signed in to change notification settings - Fork 1.7k
[core-api][experimental] get_asset_provenance
#26684
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
OwenKephart
merged 2 commits into
core-api-audit
from
12-23-_core-api_experimental_get_asset_provenance_
Feb 6, 2025
Merged
[core-api][experimental] get_asset_provenance
#26684
OwenKephart
merged 2 commits into
core-api-audit
from
12-23-_core-api_experimental_get_asset_provenance_
Feb 6, 2025
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Dec 23, 2024
This was referenced Dec 23, 2024
This was referenced Dec 23, 2024
Base automatically changed from
12-23-_core-api_experimental_assetout_tags
to
12-23-_core-api_experimental_owners_
December 31, 2024 19:24
Base automatically changed from
12-23-_core-api_experimental_owners_
to
12-23-_core-api_experimental_report_runless_asset_event_
December 31, 2024 19:24
Base automatically changed from
12-23-_core-api_experimental_report_runless_asset_event_
to
12-23-_core-api_experimental_exclude_subruns
December 31, 2024 19:24
Base automatically changed from
12-23-_core-api_experimental_exclude_subruns
to
12-23-_core-api_experimental_build_reconstructable_job_
December 31, 2024 19:25
Base automatically changed from
12-23-_core-api_experimental_build_reconstructable_job_
to
12-23-_core-api_experimental_source_code_metadata
December 31, 2024 19:25
Base automatically changed from
12-23-_core-api_experimental_source_code_metadata
to
12-23-_core-api_experimental_automationconditionsensordefinition
December 31, 2024 19:25
Base automatically changed from
12-23-_core-api_experimental_automationconditionsensordefinition
to
12-23-_core-api_experimental_multi_asset_sensor
December 31, 2024 19:25
Base automatically changed from
12-23-_core-api_experimental_multi_asset_sensor
to
12-23-_core-api_experimental_observeresult
December 31, 2024 19:25
Base automatically changed from
12-23-_core-api_experimental_observeresult
to
12-23-_core-apis_experimental_automationcondition.any_downstream_conditions
December 31, 2024 19:26
Base automatically changed from
12-23-_core-apis_experimental_automationcondition.any_downstream_conditions
to
core-api-audit
December 31, 2024 19:26
efa7c18
to
28e73c5
Compare
07509f0
to
7611d3a
Compare
smackesey
approved these changes
Jan 2, 2025
28e73c5
to
655ae75
Compare
7611d3a
to
fdd99dc
Compare
655ae75
to
f2e00af
Compare
8f05c61
to
6b1aae6
Compare
6b1aae6
to
d243e7e
Compare
maximearmstrong
approved these changes
Feb 5, 2025
f2e00af
to
7a526b2
Compare
d243e7e
to
74478c0
Compare
## Summary & Motivation decision: experimental -> beta reason: this requires a final pass on our end to feel comfortable marking as GA, but I think it is worth doing in the near future as this is a powerful feature docs exist: no (will need to) ## How I Tested These Changes ## Changelog > Insert changelog entry or delete this section.
OwenKephart
added a commit
that referenced
this pull request
Feb 6, 2025
## Summary & Motivation decision: experimental -> public (uncertain) reason: this has existed for years without change. even if this is not a commonly-used API, we should probably just make the call that we're not changing it at this point docs exist: yes (api only, which is ok) ## How I Tested These Changes ## Changelog > Insert changelog entry or delete this section.
OwenKephart
added a commit
that referenced
this pull request
Feb 6, 2025
## Summary & Motivation decision: experimental -> public (uncertain) reason: this has existed for years without change. even if this is not a commonly-used API, we should probably just make the call that we're not changing it at this point docs exist: yes (api only, which is ok) ## How I Tested These Changes ## Changelog > Insert changelog entry or delete this section.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary & Motivation
decision: experimental -> public (uncertain)
reason: this has existed for years without change. even if this is not a commonly-used API, we should probably just make the call that we're not changing it at this point
docs exist: yes (api only, which is ok)
How I Tested These Changes
Changelog