You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "olegkachur-e (via GitHub)" <gi...@apache.org> on 2026/03/26 10:41:48 UTC

[PR] Rename Cloud Composer service in the operator docs [airflow]

olegkachur-e opened a new pull request, #64257:
URL: https://github.com/apache/airflow/pull/64257

   - Rename "Cloud composer" into the "Managed Service for Apache Airflow (formerly Cloud Composer)".
   
   As a decision of Cloud composer team.
   
    <!-- SPDX-License-Identifier: Apache-2.0
         https://www.apache.org/licenses/LICENSE-2.0 -->
   
   <!--
   Thank you for contributing!
   
   Please provide above a brief description of the changes made in this pull request.
   Write a good git commit message following this guide: http://chris.beams.io/posts/git-commit/
   
   Please make sure that your code changes are covered with tests.
   And in case of new features or big changes remember to adjust the documentation.
   
   Feel free to ping (in general) for the review if you do not see reaction for a few days
   (72 Hours is the minimum reaction time you can expect from volunteers) - we sometimes miss notifications.
   
   In case of an existing issue, reference it using one of the following:
   
   * closes: #ISSUE
   * related: #ISSUE
   -->
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   <!--
   If generative AI tooling has been used in the process of authoring this PR, please
   change below checkbox to `[X]` followed by the name of the tool, uncomment the "Generated-by".
   -->
   
   - [ ] Yes (please specify the tool below)
   
   <!--
   Generated-by: [Tool Name] following [the guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
   -->
   
   ---
   
   * Read the **[Pull Request Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#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](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals)) is needed.
   * When adding dependency, check compliance with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x).
   * For significant user-facing changes create newsfragment: `{pr_number}.significant.rst`, in [airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments). You can add this file in a follow-up commit after the PR is created so you know the PR number.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] Rename Cloud Composer service in the operator docs [airflow]

Posted by "eladkal (via GitHub)" <gi...@apache.org>.
eladkal commented on code in PR #64257:
URL: https://github.com/apache/airflow/pull/64257#discussion_r2997299809


##########
providers/google/docs/operators/cloud/cloud_composer.rst:
##########
@@ -15,17 +15,17 @@
     specific language governing permissions and limitations
     under the License.
 
-Google Cloud Composer Operators
-===============================
+Managed Service for Apache Airflow (formerly Cloud Composer) Operators

Review Comment:
   is that an official name change of the service? can you share public page of google confirming this name?



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] Rename Cloud Composer service in the operator docs [airflow]

Posted by "olegkachur-e (via GitHub)" <gi...@apache.org>.
olegkachur-e commented on code in PR #64257:
URL: https://github.com/apache/airflow/pull/64257#discussion_r3032750630


##########
providers/google/docs/operators/cloud/cloud_composer.rst:
##########
@@ -15,17 +15,17 @@
     specific language governing permissions and limitations
     under the License.
 
-Google Cloud Composer Operators
-===============================
+Managed Service for Apache Airflow (formerly Cloud Composer) Operators
+======================================================================

Review Comment:
   The name should be exactly as provided, due to renaming convention that will be announced.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] Rename Cloud Composer service in the operator docs [airflow]

Posted by "michalmodras (via GitHub)" <gi...@apache.org>.
michalmodras commented on PR #64257:
URL: https://github.com/apache/airflow/pull/64257#issuecomment-4282038445

   > 2. As the term is also used in other parts of the repository (bug report issue template, comments, etc.) - I'd like to ask creating PRs for these areas as well, at earliest convenience.
   
   Yes, we'll handle that shortly.
   
   > 3. I'll assume that you also plan to open PRs for renaming the relevant modules according to the [deprecation process](https://airflow.apache.org/docs/apache-airflow-providers-google/stable/deprecation-policy.html) - maybe we should add a few words about renaming modules in the policy. 
   
   No, we don't have immediate plans for this. On Google Cloud side, while the official product name (as visible in user interface, documentation) changes to Managed Service for Apache Airflow, the APIs remain to be composer.googleapis.com in the nearest future. To keep things consistent and avoid breaking user workloads, we shouldn't do renaming of the modules or operators. What we could and will consider, is adding aliases to enable naming the operators in the new way, but the old way should remain functional.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] Rename Cloud Composer service in the operator docs [airflow]

Posted by "olegkachur-e (via GitHub)" <gi...@apache.org>.
olegkachur-e commented on code in PR #64257:
URL: https://github.com/apache/airflow/pull/64257#discussion_r3032753605


##########
providers/google/docs/operators/cloud/cloud_composer.rst:
##########
@@ -15,17 +15,17 @@
     specific language governing permissions and limitations
     under the License.
 
-Google Cloud Composer Operators
-===============================
+Managed Service for Apache Airflow (formerly Cloud Composer) Operators
+======================================================================
 
-Cloud Composer is a fully managed workflow orchestration service, enabling you to create, schedule, monitor,
+Managed Service for Apache Airflow (formerly Cloud Composer) is a fully managed workflow orchestration service, enabling you to create, schedule, monitor,
 and manage workflows that span across clouds and on-premises data centers.
 
-Cloud Composer is built on the popular Apache Airflow open source project and operates using the
+Managed Service for Apache Airflow (formerly Cloud Composer) is built on the popular Apache Airflow open source project and operates using the
 Python programming language.
 
-By using Cloud Composer instead of a local instance of Apache Airflow, you can benefit from the best of
-Airflow with no installation or management overhead. Cloud Composer helps you create Airflow
+By using Managed Service for Apache Airflow (formerly Cloud Composer) instead of a local instance of Apache Airflow, you can benefit from the best of
+Airflow with no installation or management overhead. Managed Service for Apache Airflow (formerly Cloud Composer) helps you create Airflow
 environments quickly and use Airflow-native tools, such as the powerful Airflow web interface and
 command-line tools, so you can focus on your workflows and not your infrastructure.

Review Comment:
   This follows renaming convention to avoid misunderstanding between legacy and new name



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] Rename Cloud Composer service in the operator docs [airflow]

Posted by "shahar1 (via GitHub)" <gi...@apache.org>.
shahar1 merged PR #64257:
URL: https://github.com/apache/airflow/pull/64257


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] Rename Cloud Composer service in the operator docs [airflow]

Posted by "olegkachur-e (via GitHub)" <gi...@apache.org>.
olegkachur-e commented on code in PR #64257:
URL: https://github.com/apache/airflow/pull/64257#discussion_r3032759087


##########
providers/google/docs/operators/cloud/cloud_composer.rst:
##########
@@ -15,17 +15,17 @@
     specific language governing permissions and limitations
     under the License.
 
-Google Cloud Composer Operators
-===============================
+Managed Service for Apache Airflow (formerly Cloud Composer) Operators
+======================================================================
 
-Cloud Composer is a fully managed workflow orchestration service, enabling you to create, schedule, monitor,
+Managed Service for Apache Airflow (formerly Cloud Composer) is a fully managed workflow orchestration service, enabling you to create, schedule, monitor,
 and manage workflows that span across clouds and on-premises data centers.
 
-Cloud Composer is built on the popular Apache Airflow open source project and operates using the
+Managed Service for Apache Airflow (formerly Cloud Composer) is built on the popular Apache Airflow open source project and operates using the
 Python programming language.
 
-By using Cloud Composer instead of a local instance of Apache Airflow, you can benefit from the best of
-Airflow with no installation or management overhead. Cloud Composer helps you create Airflow
+By using Managed Service for Apache Airflow (formerly Cloud Composer) instead of a local instance of Apache Airflow, you can benefit from the best of
+Airflow with no installation or management overhead. Managed Service for Apache Airflow (formerly Cloud Composer) helps you create Airflow

Review Comment:
   I'll investigate possibilities to improve readability but keep the correct naming.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] Rename Cloud Composer service in the operator docs [airflow]

Posted by "shahar1 (via GitHub)" <gi...@apache.org>.
shahar1 commented on PR #64257:
URL: https://github.com/apache/airflow/pull/64257#issuecomment-4282390353

   > > 2. As the term is also used in other parts of the repository (bug report issue template, comments, etc.) - I'd like to ask creating PRs for these areas as well, at earliest convenience.
   > 
   > Yes, we'll handle that shortly.
   > 
   > > 3. I'll assume that you also plan to open PRs for renaming the relevant modules according to the [deprecation process](https://airflow.apache.org/docs/apache-airflow-providers-google/stable/deprecation-policy.html) - maybe we should add a few words about renaming modules in the policy. 
   > 
   > No, we don't have immediate plans for this. On Google Cloud side, while the official product name (as visible in user interface, documentation) changes to Managed Service for Apache Airflow, the APIs remain to be composer.googleapis.com in the nearest future. To keep things consistent and avoid breaking user workloads, we shouldn't do renaming of the modules or operators. What we could and will consider, is adding aliases to enable naming the operators in the new way, but the old way should remain functional.
   
   Thanks for your feedback Michal!
   I deliberately separated bullet 3 from 2, as the former is indeed more "long-term" thing.
   
   My main concern is that when the change eventually becomes in the API level - it will be forgotten until someone notices, and it might even be renamed again by then (see the case of "Stackdriver").
   
   Aliasing it for now will be great - we just need to pay attention if the API changes one day :)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] Rename Cloud Composer service in the operator docs [airflow]

Posted by "michalmodras (via GitHub)" <gi...@apache.org>.
michalmodras commented on PR #64257:
URL: https://github.com/apache/airflow/pull/64257#issuecomment-4266483778

   The name has been officially changed, see https://docs.cloud.google.com/composer/docs.
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] Rename Cloud Composer service in the operator docs [airflow]

Posted by "VladaZakharova (via GitHub)" <gi...@apache.org>.
VladaZakharova commented on code in PR #64257:
URL: https://github.com/apache/airflow/pull/64257#discussion_r3000443837


##########
providers/google/docs/operators/cloud/cloud_composer.rst:
##########
@@ -15,17 +15,17 @@
     specific language governing permissions and limitations
     under the License.
 
-Google Cloud Composer Operators
-===============================
+Managed Service for Apache Airflow (formerly Cloud Composer) Operators

Review Comment:
   @michalmodras 
   Can you please provide some ETA for this public documentation that is in progress rn?



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] Rename Cloud Composer service in the operator docs [airflow]

Posted by "potiuk (via GitHub)" <gi...@apache.org>.
potiuk commented on code in PR #64257:
URL: https://github.com/apache/airflow/pull/64257#discussion_r3023245179


##########
providers/google/docs/operators/cloud/cloud_composer.rst:
##########
@@ -15,17 +15,17 @@
     specific language governing permissions and limitations
     under the License.
 
-Google Cloud Composer Operators
-===============================
+Managed Service for Apache Airflow (formerly Cloud Composer) Operators

Review Comment:
   Yeah. Converting it to Draft.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] Rename Cloud Composer service in the operator docs [airflow]

Posted by "Copilot (via GitHub)" <gi...@apache.org>.
Copilot commented on code in PR #64257:
URL: https://github.com/apache/airflow/pull/64257#discussion_r3025328020


##########
providers/google/docs/operators/cloud/cloud_composer.rst:
##########
@@ -15,17 +15,17 @@
     specific language governing permissions and limitations
     under the License.
 
-Google Cloud Composer Operators
-===============================
+Managed Service for Apache Airflow (formerly Cloud Composer) Operators
+======================================================================
 
-Cloud Composer is a fully managed workflow orchestration service, enabling you to create, schedule, monitor,
+Managed Service for Apache Airflow (formerly Cloud Composer) is a fully managed workflow orchestration service, enabling you to create, schedule, monitor,
 and manage workflows that span across clouds and on-premises data centers.
 
-Cloud Composer is built on the popular Apache Airflow open source project and operates using the
+Managed Service for Apache Airflow (formerly Cloud Composer) is built on the popular Apache Airflow open source project and operates using the
 Python programming language.
 
-By using Cloud Composer instead of a local instance of Apache Airflow, you can benefit from the best of
-Airflow with no installation or management overhead. Cloud Composer helps you create Airflow
+By using Managed Service for Apache Airflow (formerly Cloud Composer) instead of a local instance of Apache Airflow, you can benefit from the best of
+Airflow with no installation or management overhead. Managed Service for Apache Airflow (formerly Cloud Composer) helps you create Airflow
 environments quickly and use Airflow-native tools, such as the powerful Airflow web interface and
 command-line tools, so you can focus on your workflows and not your infrastructure.

Review Comment:
   Several lines become very long after expanding the product name, which hurts readability and may violate documentation linters (e.g., line-length checks). Please reflow/wrap these sentences so the product name doesn’t create oversized lines (split after natural clause boundaries).
   ```suggestion
   By using Managed Service for Apache Airflow (formerly Cloud Composer)
   instead of a local instance of Apache Airflow, you can benefit from the
   best of Airflow with no installation or management overhead.
   Managed Service for Apache Airflow (formerly Cloud Composer) helps you
   create Airflow environments quickly and use Airflow-native tools, such as
   the powerful Airflow web interface and command-line tools, so you can
   focus on your workflows and not your infrastructure.
   ```



##########
providers/google/docs/operators/cloud/cloud_composer.rst:
##########
@@ -15,17 +15,17 @@
     specific language governing permissions and limitations
     under the License.
 
-Google Cloud Composer Operators
-===============================
+Managed Service for Apache Airflow (formerly Cloud Composer) Operators
+======================================================================
 
-Cloud Composer is a fully managed workflow orchestration service, enabling you to create, schedule, monitor,
+Managed Service for Apache Airflow (formerly Cloud Composer) is a fully managed workflow orchestration service, enabling you to create, schedule, monitor,
 and manage workflows that span across clouds and on-premises data centers.
 
-Cloud Composer is built on the popular Apache Airflow open source project and operates using the
+Managed Service for Apache Airflow (formerly Cloud Composer) is built on the popular Apache Airflow open source project and operates using the
 Python programming language.
 
-By using Cloud Composer instead of a local instance of Apache Airflow, you can benefit from the best of
-Airflow with no installation or management overhead. Cloud Composer helps you create Airflow
+By using Managed Service for Apache Airflow (formerly Cloud Composer) instead of a local instance of Apache Airflow, you can benefit from the best of
+Airflow with no installation or management overhead. Managed Service for Apache Airflow (formerly Cloud Composer) helps you create Airflow

Review Comment:
   The expanded product name is repeated multiple times in the intro, making future edits and readability harder. Consider introducing the full name once, then using a shorter consistent form afterward (e.g., 'Managed Service for Apache Airflow' or 'Cloud Composer' as a parenthetical alias) to reduce repetition while still honoring the naming decision.



##########
providers/google/docs/operators/cloud/cloud_composer.rst:
##########
@@ -15,17 +15,17 @@
     specific language governing permissions and limitations
     under the License.
 
-Google Cloud Composer Operators
-===============================
+Managed Service for Apache Airflow (formerly Cloud Composer) Operators
+======================================================================

Review Comment:
   The new heading removes the explicit 'Google' qualifier that existed in 'Google Cloud Composer Operators'. Since 'Managed Service for Apache Airflow' can be interpreted generically, consider keeping a Google qualifier in the title (e.g., 'Google Managed Service for Apache Airflow … Operators') to avoid ambiguity in cross-provider docs.
   ```suggestion
   Google Managed Service for Apache Airflow (formerly Cloud Composer) Operators
   =============================================================================
   ```



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] Rename Cloud Composer service in the operator docs [airflow]

Posted by "olegkachur-e (via GitHub)" <gi...@apache.org>.
olegkachur-e commented on code in PR #64257:
URL: https://github.com/apache/airflow/pull/64257#discussion_r3009039006


##########
providers/google/docs/operators/cloud/cloud_composer.rst:
##########
@@ -15,17 +15,17 @@
     specific language governing permissions and limitations
     under the License.
 
-Google Cloud Composer Operators
-===============================
+Managed Service for Apache Airflow (formerly Cloud Composer) Operators

Review Comment:
   @eladkal Fair enough! :-) To the best of my knowledge, we should see those official Google doc updates in the middle of April 2026.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] Rename Cloud Composer service in the operator docs [airflow]

Posted by "eladkal (via GitHub)" <gi...@apache.org>.
eladkal commented on code in PR #64257:
URL: https://github.com/apache/airflow/pull/64257#discussion_r3009239417


##########
providers/google/docs/operators/cloud/cloud_composer.rst:
##########
@@ -15,17 +15,17 @@
     specific language governing permissions and limitations
     under the License.
 
-Google Cloud Composer Operators
-===============================
+Managed Service for Apache Airflow (formerly Cloud Composer) Operators

Review Comment:
   I think we should wait for Google to officially declare a name change.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org