Automated Canary Release Rollback Orchestrator Generator

Role: Principal Site Reliability Engineer & Platform Operations Architect

Context

• Target Microservice: {{service_name}}
• Runtime Environment: {{deployment_environment}}
• Health Metric Boundaries: {{telemetry_thresholds}}
• Deployment Infrastructure: {{orchestration_engine}}
• Alerting Channel Integration: {{pagerduty_service_key}}
• Rollback Execution Protocol: {{rollback_strategy}}

Task

Generate an executable, production-grade Bash and API orchestration script that monitors canary health against defined metric boundaries, executes an immediate zero-downtime rollback if degradation occurs, and logs execution telemetry to incident responders.

Method

1. Initialize safe execution defaults (set -euo pipefail) and parse environment runtime credentials.
2. Ingest {{telemetry_thresholds}} and initialize active polling against Prometheus or Datadog APIs.
3. Implement a bounded polling loop evaluating sliding window metrics against baseline criteria.
4. Define an evaluation branch assessing canary HTTP 5xx rates, P99 latency, and host resource utilization.
5. Upon anomaly detection, invoke {{orchestration_engine}} API endpoints to instantly divert ingress traffic back to stable baseline pods.
6. Execute the {{rollback_strategy}} sequence to terminate degraded canary instances safely without connection drops.
7. Dispatch an automated high-urgency incident payload to {{pagerduty_service_key}} containing trigger metrics, blast radius stats, and pod execution logs.
8. Emit structured JSON execution logs detailing script start time, metric snapshots, mitigation timestamps, and final cluster state.

Constraints

• MUST include rigorous error trapping and exit traps to ensure no orphaned canary containers remain active on failure.
• MUST NOT expose raw API credentials or tokens; extract them strictly from injected environment secrets.
• Script logic MUST be fully idempotent so repeated executions do not corrupt production deployment state.
• Do not use non-standard shell dependencies beyond curl, jq, and core system utilities.

Output format

Provide the deliverable in two strict sections:

1. SCRIPT_HEADER: Configuration block defining environment variables, threshold constants, and dependency validation.
2. SCRIPT_BODY: Complete, comment-annotated POSIX-compliant Bash script (under 250 lines) formatted within a single code block.

Self-review

• Ensure every shell parameter expansion is quoted to prevent injection vulnerabilities.
• Verify API query syntax against the declared {{orchestration_engine}} spec.
• Confirm all exit codes map distinctly to successful rollback, telemetry timeout, or API communication errors.