Label all resources in lineage events #16471
Open
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.
We changed how we decide if a resource on an event is a "lineage" resource. Now, a resource must have the
prefect.resource.lineage-group
label to be considered a lineage resource. In order to capture lineage relationships with flows and other objects, we attachprefect.resource.lineage-group
to all resources passed in and all related resources we discover.NOTE: This leaves callers with no way to specify that a resource is related but not a lineage resource. In the short term, this is OK. In the long term, one way that users might specify this is adding
prefect.resource.lineage-group=None
to resources they want to appear in the event but not on the lineage dashboard.Checklist
<link to issue>
"mint.json
.