From 69bead8ee9f9d0c162c5d71250b3239b4bc44b94 Mon Sep 17 00:00:00 2001 From: Rounak Dhillon <162090200+RounakDhillon@users.noreply.github.com> Date: Thu, 17 Jul 2025 18:23:04 +0530 Subject: [PATCH] Docs: Correcting GCS Composer to GCP Composer (#22429) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit * Docs: Correcting GCS Composer to GCP Composer * Docs: Correcting GCS Composer to GCP Composer --------- Co-authored-by: “Rounak <“rounakpreet.d@deuexsolutions.com”> --- openmetadata-docs/content/v1.7.x/collate-menu.md | 8 ++++---- .../airflow/{gcs-composer.md => gcp-composer.md} | 10 +++++----- .../v1.7.x/connectors/pipeline/airflow/index.md | 4 ++-- .../external/{gcs-composer.md => gcp-composer.md} | 12 ++++++------ .../v1.7.x/deployment/ingestion/external/index.md | 4 ++-- .../hybrid-saas/{gcs-composer.md => gcp-composer.md} | 10 +++++----- .../getting-started/day-1/hybrid-saas/index.md | 4 ++-- openmetadata-docs/content/v1.7.x/menu.md | 8 ++++---- openmetadata-docs/content/v1.8.x/collate-menu.md | 8 ++++---- .../connectors/pipeline/airflow/gcp-composer.md} | 10 +++++----- .../v1.8.x/connectors/pipeline/airflow/index.md | 4 ++-- .../external/{gcs-composer.md => gcp-composer.md} | 12 ++++++------ .../v1.8.x/deployment/ingestion/external/index.md | 4 ++-- .../hybrid-saas/{gcs-composer.md => gcp-composer.md} | 10 +++++----- .../getting-started/day-1/hybrid-saas/index.md | 4 ++-- openmetadata-docs/content/v1.8.x/menu.md | 8 ++++---- .../content/v1.9.x-SNAPSHOT/collate-menu.md | 8 ++++---- .../connectors/pipeline/airflow/gcp-composer.md} | 10 +++++----- .../connectors/pipeline/airflow/index.md | 4 ++-- .../external/{gcs-composer.md => gcp-composer.md} | 12 ++++++------ .../deployment/ingestion/external/index.md | 4 ++-- .../hybrid-saas/{gcs-composer.md => gcp-composer.md} | 10 +++++----- .../getting-started/day-1/hybrid-saas/index.md | 4 ++-- openmetadata-docs/content/v1.9.x-SNAPSHOT/menu.md | 8 ++++---- 24 files changed, 90 insertions(+), 90 deletions(-) rename openmetadata-docs/content/v1.7.x/connectors/pipeline/airflow/{gcs-composer.md => gcp-composer.md} (96%) rename openmetadata-docs/content/v1.7.x/deployment/ingestion/external/{gcs-composer.md => gcp-composer.md} (92%) rename openmetadata-docs/content/v1.7.x/getting-started/day-1/hybrid-saas/{gcs-composer.md => gcp-composer.md} (94%) rename openmetadata-docs/content/{v1.9.x-SNAPSHOT/connectors/pipeline/airflow/gcs-composer.md => v1.8.x/connectors/pipeline/airflow/gcp-composer.md} (96%) rename openmetadata-docs/content/v1.8.x/deployment/ingestion/external/{gcs-composer.md => gcp-composer.md} (92%) rename openmetadata-docs/content/v1.8.x/getting-started/day-1/hybrid-saas/{gcs-composer.md => gcp-composer.md} (94%) rename openmetadata-docs/content/{v1.8.x/connectors/pipeline/airflow/gcs-composer.md => v1.9.x-SNAPSHOT/connectors/pipeline/airflow/gcp-composer.md} (96%) rename openmetadata-docs/content/v1.9.x-SNAPSHOT/deployment/ingestion/external/{gcs-composer.md => gcp-composer.md} (92%) rename openmetadata-docs/content/v1.9.x-SNAPSHOT/getting-started/day-1/hybrid-saas/{gcs-composer.md => gcp-composer.md} (94%) diff --git a/openmetadata-docs/content/v1.7.x/collate-menu.md b/openmetadata-docs/content/v1.7.x/collate-menu.md index 8af77e7fee3..ab906477815 100644 --- a/openmetadata-docs/content/v1.7.x/collate-menu.md +++ b/openmetadata-docs/content/v1.7.x/collate-menu.md @@ -14,8 +14,8 @@ site_menu: url: /getting-started/day-1/hybrid-saas/airflow - category: Getting Started / Day 1 / Hybrid SaaS / MWAA url: /getting-started/day-1/hybrid-saas/mwaa - - category: Getting Started / Day 1 / Hybrid SaaS / GCS Composer - url: /getting-started/day-1/hybrid-saas/gcs-composer + - category: Getting Started / Day 1 / Hybrid SaaS / GCP Composer + url: /getting-started/day-1/hybrid-saas/gcp-composer - category: Getting Started / Day 1 / Hybrid SaaS / GitHub Actions url: /getting-started/day-1/hybrid-saas/github-actions - category: Getting Started / Day 1 / Hybrid SaaS / Credentials @@ -451,8 +451,8 @@ site_menu: url: /connectors/pipeline/airflow/configuring-lineage - category: Connectors / Pipeline / Airflow / MWAA url: /connectors/pipeline/airflow/mwaa - - category: Connectors / Pipeline / Airflow / GCS Composer - url: /connectors/pipeline/airflow/gcs-composer + - category: Connectors / Pipeline / Airflow / GCP Composer + url: /connectors/pipeline/airflow/gcp-composer - category: Connectors / Pipeline / Azure Data Factory url: /connectors/pipeline/datafactory - category: Connectors / Pipeline / Azure Data Factory / Run Externally diff --git a/openmetadata-docs/content/v1.7.x/connectors/pipeline/airflow/gcs-composer.md b/openmetadata-docs/content/v1.7.x/connectors/pipeline/airflow/gcp-composer.md similarity index 96% rename from openmetadata-docs/content/v1.7.x/connectors/pipeline/airflow/gcs-composer.md rename to openmetadata-docs/content/v1.7.x/connectors/pipeline/airflow/gcp-composer.md index c676cbb29b7..415a98f4638 100644 --- a/openmetadata-docs/content/v1.7.x/connectors/pipeline/airflow/gcs-composer.md +++ b/openmetadata-docs/content/v1.7.x/connectors/pipeline/airflow/gcp-composer.md @@ -1,9 +1,9 @@ --- -title: Extract Metadata from GCS Composer -slug: /connectors/pipeline/airflow/gcs-composer +title: Extract Metadata from GCP Composer +slug: /connectors/pipeline/airflow/gcp-composer --- -# Extract Metadata from GCS Composer +# Extract Metadata from GCP Composer ## Requirements @@ -20,7 +20,7 @@ Feel free to choose whatever approach adapts best to your current architecture a ## Using the Python Operator -The most comfortable way to extract metadata out of GCS Composer is by directly creating a DAG in there +The most comfortable way to extract metadata out of GCP Composer is by directly creating a DAG in there that will handle the connection to the metadata database automatically and push the contents to your OpenMetadata server. @@ -129,7 +129,7 @@ with DAG( ## Using the Kubernetes Pod Operator -In this second approach we won't need to install absolutely anything to the GCS Composer environment. Instead, +In this second approach we won't need to install absolutely anything to the GCP Composer environment. Instead, we will rely on the `KubernetesPodOperator` to use the underlying k8s cluster of Composer. Then, the code won't directly run using the hosts' environment, but rather inside a container that we created diff --git a/openmetadata-docs/content/v1.7.x/connectors/pipeline/airflow/index.md b/openmetadata-docs/content/v1.7.x/connectors/pipeline/airflow/index.md index 5900cfc8a23..916a09500dd 100644 --- a/openmetadata-docs/content/v1.7.x/connectors/pipeline/airflow/index.md +++ b/openmetadata-docs/content/v1.7.x/connectors/pipeline/airflow/index.md @@ -27,8 +27,8 @@ Configure and schedule Airflow metadata workflow from the OpenMetadata UI: link="/deployment/ingestion/external/mwaa" / %} {% tile - title="GCS Composer" - description="Run the ingestion from GCS Composer." + title="GCP Composer " + description="Run the ingestion from GCP Composer ." link="/deployment/ingestion/external/gcs-composer" / %} {% /tilesContainer %} diff --git a/openmetadata-docs/content/v1.7.x/deployment/ingestion/external/gcs-composer.md b/openmetadata-docs/content/v1.7.x/deployment/ingestion/external/gcp-composer.md similarity index 92% rename from openmetadata-docs/content/v1.7.x/deployment/ingestion/external/gcs-composer.md rename to openmetadata-docs/content/v1.7.x/deployment/ingestion/external/gcp-composer.md index 55a27c3e9ec..7f4b21dfab2 100644 --- a/openmetadata-docs/content/v1.7.x/deployment/ingestion/external/gcs-composer.md +++ b/openmetadata-docs/content/v1.7.x/deployment/ingestion/external/gcp-composer.md @@ -1,13 +1,13 @@ --- -title: Run the ingestion from GCS Composer | Official Documentation -description: Deploy external ingestion using GCS Composer to automate metadata and quality pipelines on Google Cloud environments. -slug: /deployment/ingestion/external/gcs-composer +title: Run the ingestion from GCP Composer | Official Documentation +description: Deploy external ingestion using GCP Composer to automate metadata and quality pipelines on Google Cloud environments. +slug: /deployment/ingestion/external/gcp-composer collate: false --- {% partial file="/v1.7/deployment/external-ingestion.md" /%} -# Run the ingestion from GCS Composer +# Run the ingestion from GCP Composer ## Requirements @@ -19,7 +19,7 @@ It also requires the ingestion package to be at least `openmetadata-ingestion==1 ## Using the Python Operator -The most comfortable way to run the metadata workflows from GCS Composer is directly via a `PythonOperator`. Note that +The most comfortable way to run the metadata workflows from GCP Composer is directly via a `PythonOperator`. Note that it will require you to install the packages and plugins directly on the host. ### Install the Requirements @@ -98,7 +98,7 @@ with DAG( ## Using the Kubernetes Pod Operator -In this second approach we won't need to install absolutely anything to the GCS Composer environment. Instead, +In this second approach we won't need to install absolutely anything to the GCP Composer environment. Instead, we will rely on the `KubernetesPodOperator` to use the underlying k8s cluster of Composer. Then, the code won't directly run using the hosts' environment, but rather inside a container that we created diff --git a/openmetadata-docs/content/v1.7.x/deployment/ingestion/external/index.md b/openmetadata-docs/content/v1.7.x/deployment/ingestion/external/index.md index 87ffc553dd1..5594b4c70fe 100644 --- a/openmetadata-docs/content/v1.7.x/deployment/ingestion/external/index.md +++ b/openmetadata-docs/content/v1.7.x/deployment/ingestion/external/index.md @@ -284,9 +284,9 @@ don't hesitate to reach to us in [Slack](https://slack.open-metadata.org/) or di {% inlineCallout color="violet-70" icon="10k" - bold="GCS Composer" + bold="GCP Composer " href="/deployment/ingestion/external/gcs-composer" %} - Run the ingestion process externally from GCS Composer + Run the ingestion process externally from GCP Composer {% /inlineCallout %} {% inlineCallout color="violet-70" diff --git a/openmetadata-docs/content/v1.7.x/getting-started/day-1/hybrid-saas/gcs-composer.md b/openmetadata-docs/content/v1.7.x/getting-started/day-1/hybrid-saas/gcp-composer.md similarity index 94% rename from openmetadata-docs/content/v1.7.x/getting-started/day-1/hybrid-saas/gcs-composer.md rename to openmetadata-docs/content/v1.7.x/getting-started/day-1/hybrid-saas/gcp-composer.md index ebcd67d47f6..3b9ecee084b 100644 --- a/openmetadata-docs/content/v1.7.x/getting-started/day-1/hybrid-saas/gcs-composer.md +++ b/openmetadata-docs/content/v1.7.x/getting-started/day-1/hybrid-saas/gcp-composer.md @@ -1,12 +1,12 @@ --- -title: Run the ingestion from GCS Composer -slug: /getting-started/day-1/hybrid-saas/gcs-composer +title: Run the ingestion from GCP Composer +slug: /getting-started/day-1/hybrid-saas/gcp-composer collate: true --- {% partial file="/v1.7/deployment/external-ingestion.md" /%} -# Run the ingestion from GCS Composer +# Run the ingestion from GCP Composer ## Requirements @@ -18,7 +18,7 @@ It also requires the ingestion package to be at least `openmetadata-ingestion==1 ## Using the Python Operator -The most comfortable way to run the metadata workflows from GCS Composer is directly via a `PythonOperator`. Note that +The most comfortable way to run the metadata workflows from GCP Composer is directly via a `PythonOperator`. Note that it will require you to install the packages and plugins directly on the host. ### Install the Requirements @@ -97,7 +97,7 @@ with DAG( ## Using the Kubernetes Pod Operator -In this second approach we won't need to install absolutely anything to the GCS Composer environment. Instead, +In this second approach we won't need to install absolutely anything to the GCP Composer environment. Instead, we will rely on the `KubernetesPodOperator` to use the underlying k8s cluster of Composer. Then, the code won't directly run using the hosts' environment, but rather inside a container that we created diff --git a/openmetadata-docs/content/v1.7.x/getting-started/day-1/hybrid-saas/index.md b/openmetadata-docs/content/v1.7.x/getting-started/day-1/hybrid-saas/index.md index a20b3ea4052..98782f19d17 100644 --- a/openmetadata-docs/content/v1.7.x/getting-started/day-1/hybrid-saas/index.md +++ b/openmetadata-docs/content/v1.7.x/getting-started/day-1/hybrid-saas/index.md @@ -309,9 +309,9 @@ don't hesitate to reach to us in [Slack](https://slack.open-metadata.org/) or di {% inlineCallout color="violet-70" icon="10k" - bold="GCS Composer" + bold="GCP Composer " href="/deployment/ingestion/external/gcs-composer" %} - Run the ingestion process externally from GCS Composer + Run the ingestion process externally from GCP Composer {% /inlineCallout %} {% inlineCallout color="violet-70" diff --git a/openmetadata-docs/content/v1.7.x/menu.md b/openmetadata-docs/content/v1.7.x/menu.md index b4a75838d93..4140dc1db88 100644 --- a/openmetadata-docs/content/v1.7.x/menu.md +++ b/openmetadata-docs/content/v1.7.x/menu.md @@ -59,8 +59,8 @@ site_menu: url: /deployment/ingestion/external/airflow - category: Deployment / Ingestion / External / MWAA url: /deployment/ingestion/external/mwaa - - category: Deployment / Ingestion / External / GCS Composer - url: /deployment/ingestion/external/gcs-composer + - category: Deployment / Ingestion / External / GCP Composer + url: /deployment/ingestion/external/gcp-composer - category: Deployment / Ingestion / External / GitHub Actions url: /deployment/ingestion/external/github-actions - category: Deployment / Ingestion / External / Credentials @@ -641,8 +641,8 @@ site_menu: url: /connectors/pipeline/airflow/configuring-lineage - category: Connectors / Pipeline / Airflow / MWAA url: /connectors/pipeline/airflow/mwaa - - category: Connectors / Pipeline / Airflow / GCS Composer - url: /connectors/pipeline/airflow/gcs-composer + - category: Connectors / Pipeline / Airflow / GCP Composer + url: /connectors/pipeline/airflow/gcp-composer - category: Connectors / Pipeline / Dagster url: /connectors/pipeline/dagster - category: Connectors / Pipeline / Dagster / Run Externally diff --git a/openmetadata-docs/content/v1.8.x/collate-menu.md b/openmetadata-docs/content/v1.8.x/collate-menu.md index 6bd5d576746..a4513f6f664 100644 --- a/openmetadata-docs/content/v1.8.x/collate-menu.md +++ b/openmetadata-docs/content/v1.8.x/collate-menu.md @@ -14,8 +14,8 @@ site_menu: url: /getting-started/day-1/hybrid-saas/airflow - category: Getting Started / Day 1 / Hybrid SaaS / MWAA url: /getting-started/day-1/hybrid-saas/mwaa - - category: Getting Started / Day 1 / Hybrid SaaS / GCS Composer - url: /getting-started/day-1/hybrid-saas/gcs-composer + - category: Getting Started / Day 1 / Hybrid SaaS / GCP Composer + url: /getting-started/day-1/hybrid-saas/gcp-composer - category: Getting Started / Day 1 / Hybrid SaaS / GitHub Actions url: /getting-started/day-1/hybrid-saas/github-actions - category: Getting Started / Day 1 / Hybrid SaaS / Credentials @@ -461,8 +461,8 @@ site_menu: url: /connectors/pipeline/airflow/configuring-lineage - category: Connectors / Pipeline / Airflow / MWAA url: /connectors/pipeline/airflow/mwaa - - category: Connectors / Pipeline / Airflow / GCS Composer - url: /connectors/pipeline/airflow/gcs-composer + - category: Connectors / Pipeline / Airflow / GCP Composer + url: /connectors/pipeline/airflow/gcp-composer - category: Connectors / Pipeline / Azure Data Factory url: /connectors/pipeline/datafactory - category: Connectors / Pipeline / Azure Data Factory / Run Externally diff --git a/openmetadata-docs/content/v1.9.x-SNAPSHOT/connectors/pipeline/airflow/gcs-composer.md b/openmetadata-docs/content/v1.8.x/connectors/pipeline/airflow/gcp-composer.md similarity index 96% rename from openmetadata-docs/content/v1.9.x-SNAPSHOT/connectors/pipeline/airflow/gcs-composer.md rename to openmetadata-docs/content/v1.8.x/connectors/pipeline/airflow/gcp-composer.md index c676cbb29b7..415a98f4638 100644 --- a/openmetadata-docs/content/v1.9.x-SNAPSHOT/connectors/pipeline/airflow/gcs-composer.md +++ b/openmetadata-docs/content/v1.8.x/connectors/pipeline/airflow/gcp-composer.md @@ -1,9 +1,9 @@ --- -title: Extract Metadata from GCS Composer -slug: /connectors/pipeline/airflow/gcs-composer +title: Extract Metadata from GCP Composer +slug: /connectors/pipeline/airflow/gcp-composer --- -# Extract Metadata from GCS Composer +# Extract Metadata from GCP Composer ## Requirements @@ -20,7 +20,7 @@ Feel free to choose whatever approach adapts best to your current architecture a ## Using the Python Operator -The most comfortable way to extract metadata out of GCS Composer is by directly creating a DAG in there +The most comfortable way to extract metadata out of GCP Composer is by directly creating a DAG in there that will handle the connection to the metadata database automatically and push the contents to your OpenMetadata server. @@ -129,7 +129,7 @@ with DAG( ## Using the Kubernetes Pod Operator -In this second approach we won't need to install absolutely anything to the GCS Composer environment. Instead, +In this second approach we won't need to install absolutely anything to the GCP Composer environment. Instead, we will rely on the `KubernetesPodOperator` to use the underlying k8s cluster of Composer. Then, the code won't directly run using the hosts' environment, but rather inside a container that we created diff --git a/openmetadata-docs/content/v1.8.x/connectors/pipeline/airflow/index.md b/openmetadata-docs/content/v1.8.x/connectors/pipeline/airflow/index.md index db8ff31b141..4096728fa1e 100644 --- a/openmetadata-docs/content/v1.8.x/connectors/pipeline/airflow/index.md +++ b/openmetadata-docs/content/v1.8.x/connectors/pipeline/airflow/index.md @@ -27,8 +27,8 @@ Configure and schedule Airflow metadata workflow from the OpenMetadata UI: link="/deployment/ingestion/external/mwaa" / %} {% tile - title="GCS Composer" - description="Run the ingestion from GCS Composer." + title="GCP Composer " + description="Run the ingestion from GCP Composer ." link="/deployment/ingestion/external/gcs-composer" / %} {% /tilesContainer %} diff --git a/openmetadata-docs/content/v1.8.x/deployment/ingestion/external/gcs-composer.md b/openmetadata-docs/content/v1.8.x/deployment/ingestion/external/gcp-composer.md similarity index 92% rename from openmetadata-docs/content/v1.8.x/deployment/ingestion/external/gcs-composer.md rename to openmetadata-docs/content/v1.8.x/deployment/ingestion/external/gcp-composer.md index b669a809437..f0918e5b6cd 100644 --- a/openmetadata-docs/content/v1.8.x/deployment/ingestion/external/gcs-composer.md +++ b/openmetadata-docs/content/v1.8.x/deployment/ingestion/external/gcp-composer.md @@ -1,13 +1,13 @@ --- -title: Run the ingestion from GCS Composer | Official Documentation -description: Deploy external ingestion using GCS Composer to automate metadata and quality pipelines on Google Cloud environments. -slug: /deployment/ingestion/external/gcs-composer +title: Run the ingestion from GCP Composer | Official Documentation +description: Deploy external ingestion using GCP Composer to automate metadata and quality pipelines on Google Cloud environments. +slug: /deployment/ingestion/external/gcp-composer collate: false --- {% partial file="/v1.8/deployment/external-ingestion.md" /%} -# Run the ingestion from GCS Composer +# Run the ingestion from GCP Composer ## Requirements @@ -19,7 +19,7 @@ It also requires the ingestion package to be at least `openmetadata-ingestion==1 ## Using the Python Operator -The most comfortable way to run the metadata workflows from GCS Composer is directly via a `PythonOperator`. Note that +The most comfortable way to run the metadata workflows from GCP Composer is directly via a `PythonOperator`. Note that it will require you to install the packages and plugins directly on the host. ### Install the Requirements @@ -98,7 +98,7 @@ with DAG( ## Using the Kubernetes Pod Operator -In this second approach we won't need to install absolutely anything to the GCS Composer environment. Instead, +In this second approach we won't need to install absolutely anything to the GCP Composer environment. Instead, we will rely on the `KubernetesPodOperator` to use the underlying k8s cluster of Composer. Then, the code won't directly run using the hosts' environment, but rather inside a container that we created diff --git a/openmetadata-docs/content/v1.8.x/deployment/ingestion/external/index.md b/openmetadata-docs/content/v1.8.x/deployment/ingestion/external/index.md index 859f59423a9..840786da5a5 100644 --- a/openmetadata-docs/content/v1.8.x/deployment/ingestion/external/index.md +++ b/openmetadata-docs/content/v1.8.x/deployment/ingestion/external/index.md @@ -284,9 +284,9 @@ don't hesitate to reach to us in [Slack](https://slack.open-metadata.org/) or di {% inlineCallout color="violet-70" icon="10k" - bold="GCS Composer" + bold="GCP Composer " href="/deployment/ingestion/external/gcs-composer" %} - Run the ingestion process externally from GCS Composer + Run the ingestion process externally from GCP Composer {% /inlineCallout %} {% inlineCallout color="violet-70" diff --git a/openmetadata-docs/content/v1.8.x/getting-started/day-1/hybrid-saas/gcs-composer.md b/openmetadata-docs/content/v1.8.x/getting-started/day-1/hybrid-saas/gcp-composer.md similarity index 94% rename from openmetadata-docs/content/v1.8.x/getting-started/day-1/hybrid-saas/gcs-composer.md rename to openmetadata-docs/content/v1.8.x/getting-started/day-1/hybrid-saas/gcp-composer.md index 9674948a4d9..4005fed7311 100644 --- a/openmetadata-docs/content/v1.8.x/getting-started/day-1/hybrid-saas/gcs-composer.md +++ b/openmetadata-docs/content/v1.8.x/getting-started/day-1/hybrid-saas/gcp-composer.md @@ -1,12 +1,12 @@ --- -title: Run the ingestion from GCS Composer -slug: /getting-started/day-1/hybrid-saas/gcs-composer +title: Run the ingestion from GCP Composer +slug: /getting-started/day-1/hybrid-saas/gcp-composer collate: true --- {% partial file="/v1.8/deployment/external-ingestion.md" /%} -# Run the ingestion from GCS Composer +# Run the ingestion from GCP Composer ## Requirements @@ -18,7 +18,7 @@ It also requires the ingestion package to be at least `openmetadata-ingestion==1 ## Using the Python Operator -The most comfortable way to run the metadata workflows from GCS Composer is directly via a `PythonOperator`. Note that +The most comfortable way to run the metadata workflows from GCP Composer is directly via a `PythonOperator`. Note that it will require you to install the packages and plugins directly on the host. ### Install the Requirements @@ -97,7 +97,7 @@ with DAG( ## Using the Kubernetes Pod Operator -In this second approach we won't need to install absolutely anything to the GCS Composer environment. Instead, +In this second approach we won't need to install absolutely anything to the GCP Composer environment. Instead, we will rely on the `KubernetesPodOperator` to use the underlying k8s cluster of Composer. Then, the code won't directly run using the hosts' environment, but rather inside a container that we created diff --git a/openmetadata-docs/content/v1.8.x/getting-started/day-1/hybrid-saas/index.md b/openmetadata-docs/content/v1.8.x/getting-started/day-1/hybrid-saas/index.md index 121fe069e9f..c6838225e75 100644 --- a/openmetadata-docs/content/v1.8.x/getting-started/day-1/hybrid-saas/index.md +++ b/openmetadata-docs/content/v1.8.x/getting-started/day-1/hybrid-saas/index.md @@ -309,9 +309,9 @@ don't hesitate to reach to us in [Slack](https://slack.open-metadata.org/) or di {% inlineCallout color="violet-70" icon="10k" - bold="GCS Composer" + bold="GCP Composer " href="/deployment/ingestion/external/gcs-composer" %} - Run the ingestion process externally from GCS Composer + Run the ingestion process externally from GCP Composer {% /inlineCallout %} {% inlineCallout color="violet-70" diff --git a/openmetadata-docs/content/v1.8.x/menu.md b/openmetadata-docs/content/v1.8.x/menu.md index f49feeea7c8..4a305b780b7 100644 --- a/openmetadata-docs/content/v1.8.x/menu.md +++ b/openmetadata-docs/content/v1.8.x/menu.md @@ -65,8 +65,8 @@ site_menu: url: /deployment/ingestion/external/airflow - category: Deployment / Ingestion / External / MWAA url: /deployment/ingestion/external/mwaa - - category: Deployment / Ingestion / External / GCS Composer - url: /deployment/ingestion/external/gcs-composer + - category: Deployment / Ingestion / External / GCP Composer + url: /deployment/ingestion/external/gcp-composer - category: Deployment / Ingestion / External / GitHub Actions url: /deployment/ingestion/external/github-actions - category: Deployment / Ingestion / External / Credentials @@ -647,8 +647,8 @@ site_menu: url: /connectors/pipeline/airflow/configuring-lineage - category: Connectors / Pipeline / Airflow / MWAA url: /connectors/pipeline/airflow/mwaa - - category: Connectors / Pipeline / Airflow / GCS Composer - url: /connectors/pipeline/airflow/gcs-composer + - category: Connectors / Pipeline / Airflow / GCP Composer + url: /connectors/pipeline/airflow/gcp-composer - category: Connectors / Pipeline / Dagster url: /connectors/pipeline/dagster - category: Connectors / Pipeline / Dagster / Run Externally diff --git a/openmetadata-docs/content/v1.9.x-SNAPSHOT/collate-menu.md b/openmetadata-docs/content/v1.9.x-SNAPSHOT/collate-menu.md index 6bd5d576746..a4513f6f664 100644 --- a/openmetadata-docs/content/v1.9.x-SNAPSHOT/collate-menu.md +++ b/openmetadata-docs/content/v1.9.x-SNAPSHOT/collate-menu.md @@ -14,8 +14,8 @@ site_menu: url: /getting-started/day-1/hybrid-saas/airflow - category: Getting Started / Day 1 / Hybrid SaaS / MWAA url: /getting-started/day-1/hybrid-saas/mwaa - - category: Getting Started / Day 1 / Hybrid SaaS / GCS Composer - url: /getting-started/day-1/hybrid-saas/gcs-composer + - category: Getting Started / Day 1 / Hybrid SaaS / GCP Composer + url: /getting-started/day-1/hybrid-saas/gcp-composer - category: Getting Started / Day 1 / Hybrid SaaS / GitHub Actions url: /getting-started/day-1/hybrid-saas/github-actions - category: Getting Started / Day 1 / Hybrid SaaS / Credentials @@ -461,8 +461,8 @@ site_menu: url: /connectors/pipeline/airflow/configuring-lineage - category: Connectors / Pipeline / Airflow / MWAA url: /connectors/pipeline/airflow/mwaa - - category: Connectors / Pipeline / Airflow / GCS Composer - url: /connectors/pipeline/airflow/gcs-composer + - category: Connectors / Pipeline / Airflow / GCP Composer + url: /connectors/pipeline/airflow/gcp-composer - category: Connectors / Pipeline / Azure Data Factory url: /connectors/pipeline/datafactory - category: Connectors / Pipeline / Azure Data Factory / Run Externally diff --git a/openmetadata-docs/content/v1.8.x/connectors/pipeline/airflow/gcs-composer.md b/openmetadata-docs/content/v1.9.x-SNAPSHOT/connectors/pipeline/airflow/gcp-composer.md similarity index 96% rename from openmetadata-docs/content/v1.8.x/connectors/pipeline/airflow/gcs-composer.md rename to openmetadata-docs/content/v1.9.x-SNAPSHOT/connectors/pipeline/airflow/gcp-composer.md index c676cbb29b7..415a98f4638 100644 --- a/openmetadata-docs/content/v1.8.x/connectors/pipeline/airflow/gcs-composer.md +++ b/openmetadata-docs/content/v1.9.x-SNAPSHOT/connectors/pipeline/airflow/gcp-composer.md @@ -1,9 +1,9 @@ --- -title: Extract Metadata from GCS Composer -slug: /connectors/pipeline/airflow/gcs-composer +title: Extract Metadata from GCP Composer +slug: /connectors/pipeline/airflow/gcp-composer --- -# Extract Metadata from GCS Composer +# Extract Metadata from GCP Composer ## Requirements @@ -20,7 +20,7 @@ Feel free to choose whatever approach adapts best to your current architecture a ## Using the Python Operator -The most comfortable way to extract metadata out of GCS Composer is by directly creating a DAG in there +The most comfortable way to extract metadata out of GCP Composer is by directly creating a DAG in there that will handle the connection to the metadata database automatically and push the contents to your OpenMetadata server. @@ -129,7 +129,7 @@ with DAG( ## Using the Kubernetes Pod Operator -In this second approach we won't need to install absolutely anything to the GCS Composer environment. Instead, +In this second approach we won't need to install absolutely anything to the GCP Composer environment. Instead, we will rely on the `KubernetesPodOperator` to use the underlying k8s cluster of Composer. Then, the code won't directly run using the hosts' environment, but rather inside a container that we created diff --git a/openmetadata-docs/content/v1.9.x-SNAPSHOT/connectors/pipeline/airflow/index.md b/openmetadata-docs/content/v1.9.x-SNAPSHOT/connectors/pipeline/airflow/index.md index 52ba42144c2..7f2b72e8b9b 100644 --- a/openmetadata-docs/content/v1.9.x-SNAPSHOT/connectors/pipeline/airflow/index.md +++ b/openmetadata-docs/content/v1.9.x-SNAPSHOT/connectors/pipeline/airflow/index.md @@ -27,8 +27,8 @@ Configure and schedule Airflow metadata workflow from the OpenMetadata UI: link="/deployment/ingestion/external/mwaa" / %} {% tile - title="GCS Composer" - description="Run the ingestion from GCS Composer." + title="GCP Composer " + description="Run the ingestion from GCP Composer ." link="/deployment/ingestion/external/gcs-composer" / %} {% /tilesContainer %} diff --git a/openmetadata-docs/content/v1.9.x-SNAPSHOT/deployment/ingestion/external/gcs-composer.md b/openmetadata-docs/content/v1.9.x-SNAPSHOT/deployment/ingestion/external/gcp-composer.md similarity index 92% rename from openmetadata-docs/content/v1.9.x-SNAPSHOT/deployment/ingestion/external/gcs-composer.md rename to openmetadata-docs/content/v1.9.x-SNAPSHOT/deployment/ingestion/external/gcp-composer.md index 5ff588e4626..e6d0affcccd 100644 --- a/openmetadata-docs/content/v1.9.x-SNAPSHOT/deployment/ingestion/external/gcs-composer.md +++ b/openmetadata-docs/content/v1.9.x-SNAPSHOT/deployment/ingestion/external/gcp-composer.md @@ -1,13 +1,13 @@ --- -title: Run the ingestion from GCS Composer | Official Documentation -description: Deploy external ingestion using GCS Composer to automate metadata and quality pipelines on Google Cloud environments. -slug: /deployment/ingestion/external/gcs-composer +title: Run the ingestion from GCP Composer | Official Documentation +description: Deploy external ingestion using GCP Composer to automate metadata and quality pipelines on Google Cloud environments. +slug: /deployment/ingestion/external/gcp-composer collate: false --- {% partial file="/v1.9/deployment/external-ingestion.md" /%} -# Run the ingestion from GCS Composer +# Run the ingestion from GCP Composer ## Requirements @@ -19,7 +19,7 @@ It also requires the ingestion package to be at least `openmetadata-ingestion==1 ## Using the Python Operator -The most comfortable way to run the metadata workflows from GCS Composer is directly via a `PythonOperator`. Note that +The most comfortable way to run the metadata workflows from GCP Composer is directly via a `PythonOperator`. Note that it will require you to install the packages and plugins directly on the host. ### Install the Requirements @@ -98,7 +98,7 @@ with DAG( ## Using the Kubernetes Pod Operator -In this second approach we won't need to install absolutely anything to the GCS Composer environment. Instead, +In this second approach we won't need to install absolutely anything to the GCP Composer environment. Instead, we will rely on the `KubernetesPodOperator` to use the underlying k8s cluster of Composer. Then, the code won't directly run using the hosts' environment, but rather inside a container that we created diff --git a/openmetadata-docs/content/v1.9.x-SNAPSHOT/deployment/ingestion/external/index.md b/openmetadata-docs/content/v1.9.x-SNAPSHOT/deployment/ingestion/external/index.md index 0ba5053b028..5c521ef4f29 100644 --- a/openmetadata-docs/content/v1.9.x-SNAPSHOT/deployment/ingestion/external/index.md +++ b/openmetadata-docs/content/v1.9.x-SNAPSHOT/deployment/ingestion/external/index.md @@ -284,9 +284,9 @@ don't hesitate to reach to us in [Slack](https://slack.open-metadata.org/) or di {% inlineCallout color="violet-70" icon="10k" - bold="GCS Composer" + bold="GCP Composer " href="/deployment/ingestion/external/gcs-composer" %} - Run the ingestion process externally from GCS Composer + Run the ingestion process externally from GCP Composer {% /inlineCallout %} {% inlineCallout color="violet-70" diff --git a/openmetadata-docs/content/v1.9.x-SNAPSHOT/getting-started/day-1/hybrid-saas/gcs-composer.md b/openmetadata-docs/content/v1.9.x-SNAPSHOT/getting-started/day-1/hybrid-saas/gcp-composer.md similarity index 94% rename from openmetadata-docs/content/v1.9.x-SNAPSHOT/getting-started/day-1/hybrid-saas/gcs-composer.md rename to openmetadata-docs/content/v1.9.x-SNAPSHOT/getting-started/day-1/hybrid-saas/gcp-composer.md index ecf60658d5f..2d5cd1df860 100644 --- a/openmetadata-docs/content/v1.9.x-SNAPSHOT/getting-started/day-1/hybrid-saas/gcs-composer.md +++ b/openmetadata-docs/content/v1.9.x-SNAPSHOT/getting-started/day-1/hybrid-saas/gcp-composer.md @@ -1,12 +1,12 @@ --- -title: Run the ingestion from GCS Composer -slug: /getting-started/day-1/hybrid-saas/gcs-composer +title: Run the ingestion from GCP Composer +slug: /getting-started/day-1/hybrid-saas/gcp-composer collate: true --- {% partial file="/v1.9/deployment/external-ingestion.md" /%} -# Run the ingestion from GCS Composer +# Run the ingestion from GCP Composer ## Requirements @@ -18,7 +18,7 @@ It also requires the ingestion package to be at least `openmetadata-ingestion==1 ## Using the Python Operator -The most comfortable way to run the metadata workflows from GCS Composer is directly via a `PythonOperator`. Note that +The most comfortable way to run the metadata workflows from GCP Composer is directly via a `PythonOperator`. Note that it will require you to install the packages and plugins directly on the host. ### Install the Requirements @@ -97,7 +97,7 @@ with DAG( ## Using the Kubernetes Pod Operator -In this second approach we won't need to install absolutely anything to the GCS Composer environment. Instead, +In this second approach we won't need to install absolutely anything to the GCP Composer environment. Instead, we will rely on the `KubernetesPodOperator` to use the underlying k8s cluster of Composer. Then, the code won't directly run using the hosts' environment, but rather inside a container that we created diff --git a/openmetadata-docs/content/v1.9.x-SNAPSHOT/getting-started/day-1/hybrid-saas/index.md b/openmetadata-docs/content/v1.9.x-SNAPSHOT/getting-started/day-1/hybrid-saas/index.md index 8f1887b51a9..9a4d197e83e 100644 --- a/openmetadata-docs/content/v1.9.x-SNAPSHOT/getting-started/day-1/hybrid-saas/index.md +++ b/openmetadata-docs/content/v1.9.x-SNAPSHOT/getting-started/day-1/hybrid-saas/index.md @@ -309,9 +309,9 @@ don't hesitate to reach to us in [Slack](https://slack.open-metadata.org/) or di {% inlineCallout color="violet-70" icon="10k" - bold="GCS Composer" + bold="GCP Composer " href="/deployment/ingestion/external/gcs-composer" %} - Run the ingestion process externally from GCS Composer + Run the ingestion process externally from GCP Composer {% /inlineCallout %} {% inlineCallout color="violet-70" diff --git a/openmetadata-docs/content/v1.9.x-SNAPSHOT/menu.md b/openmetadata-docs/content/v1.9.x-SNAPSHOT/menu.md index 45532e90a3d..2dd37d9ae59 100644 --- a/openmetadata-docs/content/v1.9.x-SNAPSHOT/menu.md +++ b/openmetadata-docs/content/v1.9.x-SNAPSHOT/menu.md @@ -65,8 +65,8 @@ site_menu: url: /deployment/ingestion/external/airflow - category: Deployment / Ingestion / External / MWAA url: /deployment/ingestion/external/mwaa - - category: Deployment / Ingestion / External / GCS Composer - url: /deployment/ingestion/external/gcs-composer + - category: Deployment / Ingestion / External / GCP Composer + url: /deployment/ingestion/external/gcp-composer - category: Deployment / Ingestion / External / GitHub Actions url: /deployment/ingestion/external/github-actions - category: Deployment / Ingestion / External / Credentials @@ -647,8 +647,8 @@ site_menu: url: /connectors/pipeline/airflow/configuring-lineage - category: Connectors / Pipeline / Airflow / MWAA url: /connectors/pipeline/airflow/mwaa - - category: Connectors / Pipeline / Airflow / GCS Composer - url: /connectors/pipeline/airflow/gcs-composer + - category: Connectors / Pipeline / Airflow / GCP Composer + url: /connectors/pipeline/airflow/gcp-composer - category: Connectors / Pipeline / Dagster url: /connectors/pipeline/dagster - category: Connectors / Pipeline / Dagster / Run Externally