Repository navigation
Let plugin views be scoped to specific Assets - #74609
Merged
Merged
Conversation
Asset pages could not be scoped at all. `asset` resolved no record, so every `applies_to` path on an asset view was unevaluable and skipped, and skipping does not narrow anything -- an asset view configured with scoping showed on every asset, which is the opposite of what its author asked for. The asset is already fetched for those pages, so it costs nothing to make it a root an `applies_to` path can name, alongside the Dag, Dag Run, Task and Task Instance records. `AssetResponse` joins the models paths are validated against, so an asset path gets the same misspelling check as any other.
bbovenzi
requested review from
choo121600,
guan404ming,
pierrejeambrun,
ryanahamilton,
shubhamraj-git and
vatsrahul1001
as code owners
October 12, 2026 19:06
boring-cyborg
Bot
added
area:plugins
area:UI
Contributor
Backport failed to create: v3-4-test. View the failure log Run detailsNote: As of Merging PRs targeted for Airflow 3.X In matter of doubt please ask in #release-management Slack channel.
You can attempt to backport this manually by running: cherry_picker 230cd8a v3-4-testThis should apply the commit to the v3-4-test branch and leave the commit in conflict state marking After you have resolved the conflicts, you can continue the backport process by running: cherry_picker --continueIf you don't have cherry-picker installed, see the installation guide. |
1 task done
vatsrahul1001
added a commit
that referenced
this pull request
Oct 18, 2026
Asset pages could not be scoped at all. `asset` resolved no record, so every `applies_to` path on an asset view was unevaluable and skipped, and skipping does not narrow anything -- an asset view configured with scoping showed on every asset, which is the opposite of what its author asked for. The asset is already fetched for those pages, so it costs nothing to make it a root an `applies_to` path can name, alongside the Dag, Dag Run, Task and Task Instance records. `AssetResponse` joins the models paths are validated against, so an asset path gets the same misspelling check as any other. (cherry picked from commit 230cd8a) Co-authored-by: Brent Bovenzi <brent@astronomer.io>
vatsrahul1001
added a commit
that referenced
this pull request
Oct 20, 2026
Asset pages could not be scoped at all. `asset` resolved no record, so every `applies_to` path on an asset view was unevaluable and skipped, and skipping does not narrow anything -- an asset view configured with scoping showed on every asset, which is the opposite of what its author asked for. The asset is already fetched for those pages, so it costs nothing to make it a root an `applies_to` path can name, alongside the Dag, Dag Run, Task and Task Instance records. `AssetResponse` joins the models paths are validated against, so an asset path gets the same misspelling check as any other. (cherry picked from commit 230cd8a) Co-authored-by: Brent Bovenzi <brent@astronomer.io>
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
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.
Let plugin
applies_towork on asset attribute. Examples:group,scheduled_dags.dag_id,watchers.name,aliases.nameproducing_tasks.task_idWas generative AI tooling used to co-author this PR?
Claude Opus 5
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.