gcp-pipeline-resource-provisioning

Provisions BigQuery, Dataform, and Dataproc resources declaratively via deployment.yaml files.

1|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/tottenjordan/me-skittles --skill gcp-pipeline-resource-provisioning-tottenjordan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gcp-pipeline-resource-provisioning
Source: https://github.com/tottenjordan/me-skittles/tree/main/gemini/gcp-pipeline-resource-provisioning
Command: npx skills add https://github.com/tottenjordan/me-skittles --skill gcp-pipeline-resource-provisioning-tottenjordan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Manually creating and configuring GCP data pipeline resources across dev, staging, and prod environments is error-prone and inconsistent. This Skill automates declarative resource provisioning through a single deployment.yaml file, keeping environment-specific configurations synchronized and reproducible. ## Core Features & Use Cases - Declarative Resource Provisioning: Define BigQuery datasets and tables, Dataform repositories and workflow configs, Dataproc clusters, and BigQuery Data Transfer Service configs in one deployment.yaml file. - Environment Management: Map dev, staging, and prod environments to their own projects, regions, variables, and secrets with automatic placeholder resolution. - Secure Secret Handling: Reference existing Secret Manager secrets via variable substitution without ever reading or exposing secret values. - Use Case: A data engineer needs to stand up a new BigQuery dataset, a DTS transfer config, and a scheduled Dataform workflow for the staging environment. The agent discovers the project and region, generates the deployment.yaml, validates it, and deploys everything with gcloud orchestration-pipelines commands. ## Quick Start Ask the agent to create a deployment.yaml that provisions a BigQuery dataset and a Dataform workflow for the dev environment, then validate and deploy it.

Frequently Asked Questions about gcp-pipeline-resource-provisioning

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I provision BigQuery datasets and tables declaratively on GCP?▼

Define bigquery.dataset and bigquery.table resources in a deployment.yaml file under the target environment, then run gcloud beta orchestration-pipelines validate and deploy. The framework creates the resources with the labels and schema you specify.

How to manage dev, staging, and prod configurations for data pipelines?▼

Use the environments block in deployment.yaml to map each environment to its own project, region, variables, and secrets. Deploy to a specific environment by passing --environment=<ENV_NAME> to the deploy command.

Can I use this instead of Terraform for GCP infrastructure?▼

This approach targets data pipeline resources like BigQuery, Dataform, Dataproc, and DTS. For general infrastructure such as VMs, networks, Kubernetes, IAM policies, or multi-cloud setups, Terraform remains the recommended tool.

How are secrets handled in deployment.yaml?▼

Secrets must already exist in Secret Manager and are declared in the secrets block as references like projects/PROJECT/secrets/NAME/versions/latest. They are substituted as {{ VAR }} placeholders, and values are never read, printed, or created by the agent.

What resource types does gcloud orchestration-pipelines support?▼

Run gcloud beta orchestration-pipelines resource-types list to see the full supported set. Common types include bigquery.dataset, bigquery.table, bigquerydatatransfer.transferConfig, dataform.repository, and dataproc.cluster.

Why does deployment validation fail for deployment.yaml?▼

Validation fails when placeholders like YOUR_PROJECT_ID are unresolved, variables are undefined, or resource definitions are syntactically incorrect. Discover actual project, region, and commit SHA values with gcloud and git commands, then rerun the validate command.