gcp-pipeline-orchestration

Generate, validate, deploy, and trigger Google Cloud Composer orchestration pipeline YAML definitions.

1|Updated Jul 4, 2026
One-click install
npx skills add https://github.com/trungenglish/SHOPWISE --skill gcp-pipeline-orchestration-trungenglish
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gcp-pipeline-orchestration
Source: https://github.com/trungenglish/SHOPWISE/tree/main/.agents/skills/gcp-pipeline-orchestration
Command: npx skills add https://github.com/trungenglish/SHOPWISE --skill gcp-pipeline-orchestration-trungenglish

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), selecting compatible Composer and Dataproc environments, and running validation, deployment, and triggering commands in the right order. This Skill automates that entire workflow and prevents common schema and configuration errors. ## Core Features & Use Cases - Pipeline Generation & Initialization: Scaffold new orchestration projects with gcloud beta orchestration-pipelines init, or update existing orchestration YAML and deployment.yaml files for dbt, Dataform, PySpark, notebooks, Python scripts, and BigQuery SQL jobs. - Environment-Aware Configuration: Query real Dataproc clusters and Composer environments via gcloud, verify compatible image versions and PyPI packages, and replace placeholders with actual project, region, and bucket values. - Validate, Deploy & Trigger: Run mandatory schema validation per environment, deploy pipelines with --local, poll for DAG readiness, trigger runs, and pause or unpause pipelines, 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 checks for an existing deployment.yaml, lists available Dataproc clusters and Composer environments, generates both YAML files with correct camelCase schema and schedule endTime, validates them, then deploys and triggers the pipeline. ## Quick Start Ask the agent to create an orchestration pipeline that runs your dbt project on a schedule and deploys it to your dev Composer environment.

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 an orchestration pipeline for Google Cloud Composer?▼

Run `gcloud beta orchestration-pipelines init <name> --environment=<env>` to scaffold the project, then define the pipeline logic in an orchestration YAML file and environment settings in deployment.yaml. Validate with `gcloud beta orchestration-pipelines validate` before deploying.

How do I schedule dbt or PySpark jobs on Cloud Composer?▼

Define actions in the orchestration YAML using the `pipeline` action with a dbt framework spec or the `pyspark` action with a Dataproc engine. Add a schedule trigger with a cron interval, startTime, and a mandatory endTime, then deploy to your Composer environment.

What files are required for GCP orchestration pipelines?▼

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

Why does orchestration pipeline validation fail on Cloud Composer?▼

Validation commonly fails due to snake_case fields instead of camelCase, missing endTime in schedules, or incompatible Composer image versions. Check that your environment runs a supported composer-3 or composer-2.16.11 image or has the orchestration-pipelines PyPI package installed.

Can I trigger a deployed Composer pipeline without redeploying?▼

Yes. Use `gcloud beta orchestration-pipelines list` to find the bundle ID of the deployed pipeline, then run the trigger command with the environment, bundle, and pipeline ID. A Python fallback script can also trigger the Airflow DAG directly via the Composer API.