Skip to content

[AIP-94] Route airflow providers get through the API server#68538

Draft
yuseok89 wants to merge 1 commit into
apache:mainfrom
yuseok89:migrate-providers-get-to-airflowctl
Draft

[AIP-94] Route airflow providers get through the API server#68538
yuseok89 wants to merge 1 commit into
apache:mainfrom
yuseok89:migrate-providers-get-to-airflowctl

Conversation

@yuseok89

Copy link
Copy Markdown
Contributor

relates: #68402

WIP — depends on providers list merging first. I'll rebase on top of it, then continue with the remaining providers commands.

Routes airflow providers get through the API server and deprecates it for the new airflowctl providers get (no single-provider endpoint, so it filters GET /providers by package name).


Was generative AI tooling used to co-author this PR?
  • Yes (please specify the tool below)
    • Opus 4.8

  • Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
  • For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
  • When adding dependency, check compliance with the ASF 3rd Party License Policy.
  • For significant user-facing changes create newsfragment: {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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant