[AIP-94] Migrate airflow dags details to the API server#68529
Open
henry3260 wants to merge 1 commit into
Open
Conversation
henry3260
requested review from
bugraoz93,
dheerajturaga and
potiuk
as code owners
41 tasks
potiuk
added
the
ready for maintainer review
henry3260
force-pushed
the
migrate-airflowctl-dags-details
branch
from
d9b53ed to
2ce118c
Compare
The airflowctl migration direction keeps the existing airflow CLI behavior unchanged and only records commands that should no longer receive new development.
henry3260
force-pushed
the
migrate-airflowctl-dags-details
branch
from
2ce118c to
c9282aa
Compare
bugraoz93
approved these changes
Jun 24, 2026
Contributor
|
Thanks Henry! |
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
3 participants
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.
What
airflow dags detailscommand through the airflowctl API client.related: #68402
Was generative AI tooling used to co-author this PR?
{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.