-
Notifications
You must be signed in to change notification settings - Fork 16.3k
Ensure that both public and ui dags endpoints map to DagService #51226
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
dstandish
merged 1 commit into
apache:main
from
astronomer:unify-api-tags-for-public-and-private
May 30, 2025
Merged
Ensure that both public and ui dags endpoints map to DagService #51226
dstandish
merged 1 commit into
apache:main
from
astronomer:unify-api-tags-for-public-and-private
May 30, 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
Previously the dags router in ui endpoint was `Dags` while public was `DAG`. This resulted in the service being generated as DagsService for UI and DagService for public. But, probably better to have them generated under same service, and not just differ by the one letter.
jason810496
approved these changes
May 30, 2025
Member
pierrejeambrun
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.
Yes, thanks
pierrejeambrun
pushed a commit
to astronomer/airflow
that referenced
this pull request
Jun 3, 2025
…he#51226) Previously the dags router in ui endpoint was `Dags` while public was `DAG`. This resulted in the service being generated as DagsService for UI and DagService for public. But, probably better to have them generated under same service, and not just differ by the one letter. (cherry picked from commit c3861e7)
Member
|
backport PR: #51345 |
pierrejeambrun
pushed a commit
to astronomer/airflow
that referenced
this pull request
Jun 3, 2025
…he#51226) Previously the dags router in ui endpoint was `Dags` while public was `DAG`. This resulted in the service being generated as DagsService for UI and DagService for public. But, probably better to have them generated under same service, and not just differ by the one letter. (cherry picked from commit c3861e7)
pierrejeambrun
added a commit
that referenced
this pull request
Jun 3, 2025
…) (#51345) Previously the dags router in ui endpoint was `Dags` while public was `DAG`. This resulted in the service being generated as DagsService for UI and DagService for public. But, probably better to have them generated under same service, and not just differ by the one letter. (cherry picked from commit c3861e7) Co-authored-by: Daniel Standish <15932138+dstandish@users.noreply.github.com>
kaxil
pushed a commit
that referenced
this pull request
Jun 3, 2025
…) (#51345) Previously the dags router in ui endpoint was `Dags` while public was `DAG`. This resulted in the service being generated as DagsService for UI and DagService for public. But, probably better to have them generated under same service, and not just differ by the one letter. (cherry picked from commit c3861e7) Co-authored-by: Daniel Standish <15932138+dstandish@users.noreply.github.com>
sanederchik
pushed a commit
to sanederchik/airflow
that referenced
this pull request
Jun 7, 2025
…he#51226) Previously the dags router in ui endpoint was `Dags` while public was `DAG`. This resulted in the service being generated as DagsService for UI and DagService for public. But, probably better to have them generated under same service, and not just differ by the one letter.
jose-lehmkuhl
pushed a commit
to jose-lehmkuhl/airflow
that referenced
this pull request
Jul 11, 2025
…he#51226) Previously the dags router in ui endpoint was `Dags` while public was `DAG`. This resulted in the service being generated as DagsService for UI and DagService for public. But, probably better to have them generated under same service, and not just differ by the one letter.
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
area:UI
Related to UI/UX. For Frontend Developers.
backport-to-v3-1-test
Mark PR with this label to backport to v3-1-test branch
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.
Previously the dags router in ui endpoint was
Dagswhile public wasDAG. This resulted in the service being generated as DagsService for UI and DagService for public. But, probably better to have them generated under same service, and not just differ by the one letter.