gcp-pipeline-orchestration

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

Updated Aug 26, 2026
One-click install
npx skills add https://github.com/SmileAfterBurn/pani-dumka-ai --skill gcp-pipeline-orchestration-smileafterburn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gcp-pipeline-orchestration
Source: https://github.com/SmileAfterBurn/pani-dumka-ai/tree/main/.gemini/skills/gcp-pipeline-orchestration
Command: npx skills add https://github.com/SmileAfterBurn/pani-dumka-ai --skill gcp-pipeline-orchestration-smileafterburn

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 the entire lifecycle so pipelines are valid, deployable, and runnable without manual trial and error. ## Core Features & Use Cases - Pipeline Generation & Update: Creates or updates orchestration pipeline YAML files supporting dbt, Dataform, PySpark, notebooks, Python scripts, and inline BigQuery SQL actions, with correct camelCase field mapping and mandatory schedule endTime values. - Environment-Aware Deployment: Discovers compatible Composer environments and Dataproc clusters via gcloud, validates image versions and PyPI packages, and fills deployment.yaml placeholders with real project, region, and bucket values. - Validation, Deploy & Trigger: Runs gcloud beta orchestration-pipelines validate for every environment, deploys with --local, polls for DAG readiness, and triggers runs with a Python fallback script for Airflow DAG triggering. - Use Case: A data engineer asks to orchestrate a dbt project that runs after a PySpark job on a schedule; the Skill scaffolds the pipeline, validates it against the dev environment, deploys it to Composer, and triggers the first run. ## Quick Start Ask the agent to create and deploy an orchestration pipeline on Google Cloud Composer for your dbt, Spark, notebook, or BigQuery SQL jobs.

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 with a pipeline name and environment to scaffold the project, then define actions like pyspark, dbt, or sql in the orchestration YAML and environment details in deployment.yaml. Validate with gcloud beta orchestration-pipelines validate before deploying.

How to schedule dbt or PySpark jobs on Cloud Composer?▼

Define a schedule trigger with a cron interval, startTime, and mandatory endTime in the orchestration YAML, then add pipeline actions for dbt via airflowWorker or pyspark actions targeting a Dataproc cluster. Deploy with gcloud beta orchestration-pipelines deploy --local.

Which Composer environments support orchestration pipelines?▼

Compatible environments run image versions like composer-3-airflow-2.11.1 or composer-2.16.11-airflow-2.10.5, or have the orchestration-pipelines PyPI package installed. Check with gcloud composer environments describe and inspect the softwareConfig imageVersion and pypiPackages fields.

Why does orchestration pipeline validation fail?▼

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

Can I trigger a Composer DAG without redeploying the pipeline?▼

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. If gcloud trigger fails, fall back to the bundled airflow_trigger.py script with project, location, environment, and dag_id arguments.