cloud-deployment

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.

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.

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.

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.

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.

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.