[AIP-94] Mark config CLI commands as migrated to airflowctl#68958
Conversation
|
will need conlict resolution on this one |
1 similar comment
|
will need conlict resolution on this one |
9a53a57 to
2049101
Compare
Under AIP-94 the remote config CLI commands are frozen so new development goes to airflowctl. Following the marker-only direction from apache#68726 , record their airflowctl counterparts for maintainers without emitting any user-facing deprecation warning. Signed-off-by: PoAn Yang <payang@apache.org>
2049101 to
585b008
Compare
|
Hi maintainer, this PR was merged without a milestone set.
|
Backport failed to create: v3-3-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 6571dce v3-3-testThis should apply the commit to the v3-3-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. |
|
Backported in #69258 |
…tl (#68958) (#69258) Under AIP-94 the remote config CLI commands are frozen so new development goes to airflowctl. Following the marker-only direction from #68726 , record their airflowctl counterparts for maintainers without emitting any user-facing deprecation warning. (cherry picked from commit 6571dce) Co-authored-by: PoAn Yang <payang@apache.org>
Under AIP-94 the remote config CLI commands are frozen so new development goes to airflowctl. Following the marker-only direction from #68726 , record their airflowctl counterparts for maintainers without emitting any user-facing deprecation warning.
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.