gcp-pipeline-orchestration

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

Updated Aug 11, 2026
One-click install
npx skills add https://github.com/Yashyasik/zexca-api --skill gcp-pipeline-orchestration-yashyasik
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gcp-pipeline-orchestration
Source: https://github.com/Yashyasik/zexca-api/tree/main/.gemini/skills/gcp-pipeline-orchestration
Command: npx skills add https://github.com/Yashyasik/zexca-api --skill gcp-pipeline-orchestration-yashyasik

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), matching a strict protobuf-based schema, and running multiple gcloud 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: Scaffolds projects with gcloud beta orchestration-pipelines init and generates orchestration YAML for dbt, Dataform, PySpark, notebooks, Python scripts, and BigQuery SQL actions. - Validation & Error Recovery: Runs gcloud beta orchestration-pipelines validate for every environment and iteratively fixes reported errors until validation passes. - Deploy & Trigger Lifecycle: Deploys pipelines with --local, polls for DAG registration, triggers runs, and supports pause/unpause, with a Python fallback script for triggering via the Airflow API. - Use Case: A data engineer asks to schedule a dbt project to run daily after a PySpark job on Dataproc; the Skill checks 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 on Google Cloud Composer that runs your dbt project on a daily schedule, then deploy and trigger it in 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 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 and schedules 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 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 validate and deploy.

What files are required for orchestration pipelines deployment?▼

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

Validation commonly fails due to snake_case fields instead of camelCase, missing required fields like owner or endTime, or using a type field instead of direct 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 if the gcloud trigger command fails?▼

Yes, use the bundled airflow_trigger.py script with project, location, Composer environment, and DAG ID arguments. It authenticates with default Google credentials and calls the Airflow REST API directly to trigger the DAG run.