land-and-deploy

Canary deployment provides automated health verification by routing a portion of production traffic to the new release and checking system health. If health checks fail, rollback options are triggered automatically to revert the deployment and maintain production stability.

A gated merge workflow for release management ensures pull requests are only merged after CI success, followed by automated deployment and health verification. This satisfies requirements for auditable deploy actions and safe, controlled releases with minimal manual intervention.

Automated rollback during production health checks is triggered when canary-driven verification detects unhealthy system status. The land-and-deploy workflow monitors post-merge deployment health and initiates rollback options automatically if production metrics indicate failure.

Land-and-deploy works specifically after a PR is created by ship automation, taking over the workflow to handle merge, production deployment, and canary-based health verification. It bridges the gap between PR creation and safe production release.

Canary-based deployment verification relies on accurate health check metrics to determine production stability. If health check endpoints are misconfigured or delayed, automated rollback may trigger false positives or miss issues, requiring careful configuration of canary thresholds and monitoring parameters.