-
Notifications
You must be signed in to change notification settings - Fork 16.4k
Structure endpoint task level resolved aliases #51481
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
pierrejeambrun
merged 2 commits into
apache:main
from
astronomer:structure-endpoint-task-level-resolved-aliases
Jun 10, 2025
Merged
Structure endpoint task level resolved aliases #51481
pierrejeambrun
merged 2 commits into
apache:main
from
astronomer:structure-endpoint-task-level-resolved-aliases
Jun 10, 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
4250aca to
96b0c8b
Compare
96b0c8b to
8871e1a
Compare
pierrejeambrun
commented
Jun 6, 2025
airflow-core/tests/unit/api_fastapi/core_api/routes/ui/test_structure.py
Show resolved
Hide resolved
Merged
bugraoz93
approved these changes
Jun 6, 2025
Contributor
bugraoz93
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great! Great addition, thanks Pierre!
Lee-W
reviewed
Jun 9, 2025
airflow-core/tests/unit/api_fastapi/core_api/routes/ui/test_structure.py
Outdated
Show resolved
Hide resolved
036f061 to
13f0d8b
Compare
Lee-W
approved these changes
Jun 10, 2025
13f0d8b to
e88030f
Compare
github-actions bot
pushed a commit
that referenced
this pull request
Jun 10, 2025
* Structure endpoint task level resolved aliases * Address PR comments (cherry picked from commit acf1e77) Co-authored-by: Pierre Jeambrun <pierrejbrun@gmail.com>
github-actions bot
pushed a commit
to aws-mwaa/upstream-to-airflow
that referenced
this pull request
Jun 10, 2025
) * Structure endpoint task level resolved aliases * Address PR comments (cherry picked from commit acf1e77) Co-authored-by: Pierre Jeambrun <pierrejbrun@gmail.com>
pierrejeambrun
added a commit
that referenced
this pull request
Jun 10, 2025
* Structure endpoint task level resolved aliases * Address PR comments (cherry picked from commit acf1e77) Co-authored-by: Pierre Jeambrun <pierrejbrun@gmail.com>
pierrejeambrun
added a commit
that referenced
this pull request
Jun 11, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area:API
Airflow's REST/HTTP API
backport-to-v3-1-test
Mark PR with this label to backport to v3-1-test branch
type:new-feature
Changelog: New Features
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.
Follow up of: #51401
Bring the same change to asset aliases. When possible (we have some registered event for the asset resolution), attach the resolved asset alias to the relevant producing task.
Same as before, unresolved outlet aliases appear at the end of the dag
Now resolved aliases appears bind to the relevant task that resolves them:
Here both task1 and task2 resolve to the same asset, both are linked
For task groups