gcp-pipeline-orchestration

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

1|Updated Aug 30, 2026
One-click install
npx skills add https://github.com/FeexSystems/3WM-SONIK-LABS --skill gcp-pipeline-orchestration-feexsystems
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gcp-pipeline-orchestration
Source: https://github.com/FeexSystems/3WM-SONIK-LABS/tree/main/.gemini/skills/gcp-pipeline-orchestration
Command: npx skills add https://github.com/FeexSystems/3WM-SONIK-LABS --skill gcp-pipeline-orchestration-feexsystems

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 Scaffolding and Generation: Initializes projects with gcloud beta orchestration-pipelines init and generates orchestration YAML for dbt, Dataform, PySpark, notebooks, Python scripts, and BigQuery SQL actions. - Environment-Aware Deployment: Discovers Dataproc clusters and Composer environments via gcloud, verifies image versions and PyPI packages, and fills deployment.yaml with real project, region, and bucket values. - Validation, Deploy, and Trigger: Validates every environment with gcloud beta orchestration-pipelines validate, deploys with --local, polls for DAG readiness, and triggers runs with a Python fallback script. - Use Case: A data engineer asks to schedule a nightly dbt run after a PySpark job; the Skill generates both YAML files with correct camelCase fields, schedule startTime/endTime, validates them, and deploys to the dev Composer environment. ## Quick Start Create an orchestration pipeline that runs my dbt project nightly on Google Cloud Composer and deploy it to the dev 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 a Google Cloud Composer orchestration pipeline?▼

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 `- pipeline:` with a dbt framework spec or `- pyspark:` with a Dataproc engine. Add a schedule trigger with a cron interval, startTime, and mandatory endTime, then deploy to a compatible Composer environment.

What files are required for orchestration pipeline deployment?▼

Two files are required: an orchestration pipeline YAML defining tasks, schedule, and defaults, 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, 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?▼

Validation commonly fails from using snake_case instead of camelCase field names, missing required fields like owner or endTime, or using a `type` field instead of direct action keys like `- pyspark:`. Fix the reported issue and re-run the validate command until it exits with code 0.

Can I trigger a deployed pipeline without redeploying?▼

Yes. Use `gcloud beta orchestration-pipelines list` to find the existing bundle ID, then run the trigger command with the environment, bundle, and pipeline ID. A fallback Python script using the Airflow REST API is also available if gcloud triggering fails.