Question

Your team uses Cloud Deploy with a delivery pipeline spanning dev, staging, and prod targets. Currently an engineer manually promotes each release from staging to prod after it has run in staging for a while. Leadership wants releases to automatically promote from staging to prod, but only after the release has soaked in staging for at least 12 hours with no issues, while still keeping a manual approval requirement on the prod target. What should you configure?

Accepted Answer

Add a Cloud Deploy Automation resource with a promote-release rule that includes a wait of 12 hours on the staging target, and keep requireApproval enabled on the prod target.

Answer

Create a Cloud Scheduler job that runs every 12 hours and calls the Cloud Deploy API to promote the latest staging release, removing the prod approval requirement.

Answer

Set a deploy hook on the staging target that sleeps for 12 hours before promoting, and disable approval on prod so the automation is not blocked.

Answer

Configure a canary deployment strategy on the staging target with a 12-hour phase duration, which will then release to prod automatically.