cloud-deployment

Coordinate Cloud Run deployments across dev, staging, and production environments.

Updated Feb 28, 2026

Search Tags:#deployment #gcp #cloud #pipeline #ci-cd #cloud-run #health-checks

Ready to run

npx skills add https://github.com/IMBurbank/ganttlet --skill cloud-deployment-imburbank

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cloud-deployment
Source: https://github.com/IMBurbank/ganttlet/tree/main/.claude/skills/cloud-deployment
Command: npx skills add https://github.com/IMBurbank/ganttlet --skill cloud-deployment-imburbank

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cloud deployment and promotion workflows across dev, staging, and production environments are error-prone and manual. This Skill standardizes artifact promotion, environment injection, and health verification to reduce risk and speed deployments.

Core Features & Use Cases

Promotable artifacts pattern: keep frontend and relay images identical across environments; inject config at deploy time.
Environment variable injection: manage OAuth client IDs, relay URLs, allowed origins via Secret Manager or env vars to ensure correct config per environment.
Cloud Run pipeline and verification: automated builds, deployments, and health checks with staged promotion, plus automated E2E checks.

Quick Start

Promote artifacts from dev to production using the documented CI workflow and health checks.

Frequently Asked Questions about cloud-deployment

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

FAQPage Schema

How do I automate Cloud Run deployments across dev, staging, and production environments?▼

Automating Cloud Run deployments requires a CI workflow that coordinates artifact promotion, environment injection via Secret Manager, and health verification. This approach standardizes pipeline stages to reduce manual errors and ensure consistent configuration across environments.

What is the promotable artifacts pattern for cloud pipelines?▼

The promotable artifacts pattern keeps frontend and relay container images identical across dev, staging, and production environments. Configuration differences are injected at deploy time using environment variables or Secret Manager, ensuring the exact same image is promoted through the pipeline.

How do I inject environment variables into Cloud Run using Secret Manager?▼

Injecting environment variables into Cloud Run uses Secret Manager to supply environment-specific config like OAuth client IDs, relay URLs, and allowed origins. The CI pipeline retrieves these secrets at deploy time to configure the identical artifact for the target environment.

How do I verify health checks in a Cloud Run CI pipeline?▼

Verifying health checks in a Cloud Run CI pipeline involves automated E2E checks and staged promotion after deployment. The pipeline confirms the service is healthy before completing the promotion, reducing the risk of deploying a faulty revision to production.

Do I need separate container images for each Cloud Run environment?▼

You do not need separate container images for each Cloud Run environment. The promotable artifacts pattern maintains a single identical image across dev, staging, and production, relying on environment injection at deploy time to apply specific configurations.

Why do manual cloud deployments fail across multiple environments?▼

Manual cloud deployments fail across multiple environments due to configuration inconsistencies and human error during promotion. Standardizing artifact promotion, environment injection via Secret Manager, and automated health verification reduces this risk and speeds up the pipeline.