Skip to content

Update Composer naming and add ManagedAirflow aliases#66001

Merged
shahar1 merged 1 commit intoapache:mainfrom
VladaZakharova:composer-renaming
May 5, 2026
Merged

Update Composer naming and add ManagedAirflow aliases#66001
shahar1 merged 1 commit intoapache:mainfrom
VladaZakharova:composer-renaming

Conversation

@VladaZakharova
Copy link
Copy Markdown
Contributor

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:

  • updates the bug report issue template deployment option
  • adds ManagedAirflow...Operator aliases for Composer operators
  • updates Composer docs

The existing CloudComposer...Operator names will continue to work.
Continuation of #64257


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

  • 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.

@VladaZakharova VladaZakharova requested a review from shahar1 as a code owner April 28, 2026 07:23
@boring-cyborg boring-cyborg Bot added area:dev-tools area:providers backport-to-v3-2-test Mark PR with this label to backport to v3-2-test branch kind:documentation provider:google Google (including GCP) related issues labels Apr 28, 2026
Comment thread providers/google/src/airflow/providers/google/cloud/operators/cloud_composer.py Outdated
@VladaZakharova
Copy link
Copy Markdown
Contributor Author

Hi @shahar1
I have updated the code according to your comment, can you please recheck? thanks

Copy link
Copy Markdown
Contributor

@shahar1 shahar1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@VladaZakharova Please fix static checks - once done and CI is green, it can be merged

@shahar1 shahar1 merged commit d984e0c into apache:main May 5, 2026
96 checks passed
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 5, 2026

Backport failed to create: v3-2-test. View the failure log Run details

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status Branch Result
v3-2-test Commit Link

You can attempt to backport this manually by running:

cherry_picker d984e0c v3-2-test

This should apply the commit to the v3-2-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.

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

Labels

area:dev-tools area:providers backport-to-v3-2-test Mark PR with this label to backport to v3-2-test branch kind:documentation provider:google Google (including GCP) related issues

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants