gcp-pipeline-orchestration

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Setting up orchestration for data pipelines on Google Cloud Composer requires correctly authoring two interdependent YAML files (an orchestration pipeline definition and a deployment.yaml), validating them against a strict schema, and deploying or triggering them with the right gcloud commands. 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 pipeline files referenced by deployment.yaml. - Schema-Guided Authoring: Generate pipeline definitions for dbt, Dataform, PySpark, notebooks, Python scripts, and BigQuery SQL using the bundled protobuf-based schema reference, with correct camelCase field mapping and mandatory schedule endTime values. - Validation, Deployment & Triggering: Validate pipelines per environment, deploy 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 wants to schedule a dbt project to run after a PySpark job on Dataproc. The Skill checks for existing setup, lists available Dataproc clusters and Composer environments, generates both YAML files, validates them, and 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 author the orchestration YAML and deployment.yaml files. Validate with `gcloud beta orchestration-pipelines validate --environment=<env>` before deploying.

How to 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 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 defaults, and a deployment.yaml at the repository root defining environments with project, region, Composer environment, and artifact storage bucket.

Why does orchestration pipeline validation fail on YAML fields?▼

Validation commonly fails when proto snake_case fields are not converted to camelCase in YAML, when schedules lack an endTime, or when timestamps include a Z suffix. Use the format YYYY-MM-DDTHH:MM:SS and camelCase keys like pipelineId and startTime.

Can I trigger a Composer DAG if the gcloud trigger command fails?▼

Yes, 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.