gcp-pipeline-orchestration

Generates, validates, deploys, and triggers Google Cloud Composer orchestration pipeline definitions.

9|Updated Jul 8, 2026
One-click install
npx skills add https://github.com/jerrylin96/dotgemini --skill gcp-pipeline-orchestration-jerrylin96
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gcp-pipeline-orchestration
Source: https://github.com/jerrylin96/dotgemini/tree/main/skills/gcp-pipeline-orchestration
Command: npx skills add https://github.com/jerrylin96/dotgemini --skill gcp-pipeline-orchestration-jerrylin96

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires google-auth, requests, and includes scripts (resource) and references (resource) components.

What problem does it solve? Setting up data pipeline orchestration on Google Cloud Composer requires correctly authoring two interdependent YAML files (an orchestration pipeline definition and a deployment.yaml), matching strict schema rules, and running multiple gcloud commands in the right order. This Skill guides the agent through that entire lifecycle so pipelines are valid, deployable, and runnable. ## Core Features & Use Cases - Pipeline Generation & Updates: Creates or updates orchestration pipeline YAML and deployment.yaml files for dbt, Dataform, PySpark, notebooks, Python scripts, and inline BigQuery SQL, following the official protobuf-based schema with camelCase field mapping. - Environment Discovery & Validation: Queries Dataproc clusters and Composer environments via gcloud, verifies compatible image versions and PyPI packages, and validates files with gcloud beta orchestration-pipelines validate before completion. - Deploy & Trigger Workflow: Deploys pipelines with --local, polls for DAG registration, triggers runs, and supports pause/unpause operations, with a Python fallback script for triggering Airflow DAGs directly. - Use Case: A data engineer asks to schedule a nightly dbt run after a PySpark job. The Skill initializes the project, discovers the correct Composer environment, generates both YAML files with proper schedules and dependencies, validates them, deploys, and triggers the first run. ## Quick Start Ask the agent to create and deploy a Cloud Composer orchestration pipeline for your dbt project or Spark job in a given GCP project and region.

Frequently Asked Questions about gcp-pipeline-orchestration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a Cloud Composer orchestration pipeline for dbt or Spark jobs?

Run `gcloud beta orchestration-pipelines init` to scaffold the project, then define actions in the orchestration YAML using keys like `pyspark:` or `pipeline:` with a dbt framework spec. Validate with `gcloud beta orchestration-pipelines validate` before deploying.

How to deploy and trigger a GCP orchestration pipeline with gcloud?

Deploy with `gcloud beta orchestration-pipelines deploy --environment=<ENV> --local`, extract the bundle ID from the output, poll with the list command until the DAG appears, then run `gcloud beta orchestration-pipelines trigger` with the environment, bundle, and pipeline ID.

What files are required for GCP orchestration pipelines?

Two files are required: an orchestration pipeline YAML defining tasks, schedules, and dependencies, and a deployment.yaml at the repository root defining environments with project, region, Composer environment, and artifact storage bucket.

Which Composer image versions support orchestration pipelines?

Supported versions include composer-3 with Airflow 3.1.7, 2.11.1, 2.10.5, or 2.9.3 builds, and composer-2.16.11 with Airflow 2.11.1, 2.10.5, or 2.9.3. Environments with the orchestration-pipelines PyPI package installed are also compatible.

Why does orchestration pipeline validation fail on schedule fields?

Validation fails when schedules lack a required endTime or use a Z suffix in timestamps. Use the format YYYY-MM-DDTHH:MM:SS without the Z, set startTime to the current date if unspecified, and always include endTime.

What to do when gcloud orchestration-pipelines trigger fails?

Use the bundled fallback script scripts/trigger/airflow_trigger.py with the project, location, Composer environment, and DAG ID from deployment.yaml. It calls the Airflow REST API directly to trigger the DAG run after waiting for deployment.