Update Composer naming and add ManagedAirflow aliases#66001
Update Composer naming and add ManagedAirflow aliases#66001shahar1 merged 1 commit intoapache:mainfrom
Conversation
d925fae to
e8c3e61
Compare
e8c3e61 to
9f1b5f3
Compare
9f1b5f3 to
c9f8128
Compare
|
Hi @shahar1 |
shahar1
left a comment
There was a problem hiding this comment.
@VladaZakharova Please fix static checks - once done and CI is green, it can be merged
c9f8128 to
4e9d896
Compare
4e9d896 to
c31846f
Compare
Backport failed to create: v3-2-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 d984e0c v3-2-testThis should apply the commit to the v3-2-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. |
Update Google provider Composer naming to reflect the Managed Service for Apache Airflow rebrand.
Please, check https://docs.cloud.google.com/composer/docs.
This PR:
The existing CloudComposer...Operator names will continue to work.
Continuation of #64257
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.