gcp-pipeline-resource-provisioning

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

Updated Aug 17, 2026
One-click install
npx skills add https://github.com/DingJun1028/esggo-kv --skill gcp-pipeline-resource-provisioning-dingjun1028
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gcp-pipeline-resource-provisioning
Source: https://github.com/DingJun1028/esggo-kv/tree/main/.agents/skills/gcp-pipeline-resource-provisioning
Command: npx skills add https://github.com/DingJun1028/esggo-kv --skill gcp-pipeline-resource-provisioning-dingjun1028

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Manually creating and configuring Google Cloud 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, ensuring environment-specific configurations stay synchronized and validated before deployment. ## Core Features & Use Cases - Declarative Resource Provisioning: Define BigQuery datasets/tables, Dataform repositories, Dataproc clusters, and BigQuery Data Transfer Service configs in one deployment.yaml file. - Multi-Environment Management: Map dev, staging, and prod environments to their own projects, regions, variables, and secrets with automatic parameter discovery via gcloud. - Secure Secrets Handling: References existing Secret Manager entries without ever reading or creating secret values, keeping sensitive data out of configuration files. - Use Case: A data engineer needs to set up a new BigQuery dataset with a DTS transfer config and a Dataform workflow for the staging environment. The Skill discovers the project ID and region, generates the deployment.yaml with proper labels and secret references, validates it, and deploys it with gcloud orchestration-pipelines. ## Quick Start Ask the agent to create a deployment.yaml that provisions a BigQuery dataset and a DTS transfer config 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 with deployment.yaml?▼

Define a bigquery.dataset resource in deployment.yaml under the target environment with a name and definition including labels. Run gcloud beta orchestration-pipelines validate, then deploy with the --environment flag to create the dataset.

How to manage secrets in GCP pipeline deployment configurations?▼

Declare secrets in the secrets block of deployment.yaml referencing existing Secret Manager paths, then substitute them with {{ SECRET_NAME }} in resource definitions. The agent never creates, reads, or prints secret values; you must create secrets manually first.

What resource types does gcloud orchestration-pipelines support?▼

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

When should I use Terraform instead of orchestration-pipelines?▼

Use Terraform for general cloud infrastructure like VMs, networks, Kubernetes, and IAM policies, or when infrastructure spans multiple cloud providers. This approach is limited to supported data pipeline resources within Google Cloud only.

Why must DTS transfer configs include a destination dataset definition?▼

Every bigquerydatatransfer.transferConfig must explicitly define its target bigquery.dataset in the same deployment.yaml with the datacloud label applied. This ensures the destination dataset's labels are patched and updated even if the dataset already exists.