deploylisted

# Deploy — Advanced Deployment Strategies ## Activate When - User invokes `/godmode:deploy` - User says "deploy with zero downtime," "canary release," "blue-green deployment" - User needs rollback strategy for a risky change - Feature flags need orchestration for a complex rollout - Database migrations or infrastructure changes require zero-downtime approach - Godmode orchestrator detects high-risk changes during `/godmode:ship` ## Workflow ### Step 1: Assess Deployment Context Characterize the change and determine the correct deployment strategy: ``` DEPLOYMENT ASSESSMENT: Change type: <application code | database migration | infrastructure | config | all> Risk level: <LOW | MEDIUM | HIGH | CRITICAL> Rollback complexity: <INSTANT | MINUTES | HOURS | DIFFICULT> Change characteristics: - [ ] Backward compatible (old code works with new data) - [ ] Forward compatible (new code works with old data) - [ ] Database schema changes involved - [ ] API contract changes (breaking/non-breaking) - [ ] Infrastructure changes (new services, topology) - [ ] Feature flags available - [ ] Stateful components affected (sessions, caches) Current environment: ``` ### Step 2: Blue-Green Deployment Two identical environments, instant switchover: ``` BLUE-GREEN DEPLOYMENT PLAN: LOAD BALANCER → routes 100% to active environment [BLUE env: v1.0 (live)] ←── current traffic [GREEN env: v1.1 (idle)] ←── deploy here, then switch ``` ### Step 3: Canary Release Route a smal