1. ⏳ Validate environment configuration
2. ⏳ Run environment safety validation
3. ⏳ Check production safety confirmation requirement
4. ⏳ Initialize Terraform
5. ⏳ Select Terraform workspace
6. ⏳ Validate Terraform configuration
7. ⏳ Generate deployment plan
8. ⏳ Review plan for safety
9. ⏳ Execute production safety confirmation (if required)
10. ⏳ Execute pre-deploy hooks
11. ⏳ Execute deployment (terraform apply)
12. ⏳ Execute post-deploy hooks
13. ⏳ Verify resources created
14. ⏳ Run post-deployment tests
15. ⏳ Generate documentation
16. ⏳ Update deployment history

Mark each step in_progress → completed as you go.

OUTPUT START MESSAGE:

🚀 STARTING: Infrastructure Deployer
Environment: {environment}
AWS Profile: {profile}
───────────────────────────────────────

EXECUTE STEPS:

1. Load configuration for environment
2. Run enhanced environment validation:

   bash plugins/faber-cloud/skills/infra-deployer/scripts/enhanced-validate-environment.sh {terraform_dir} {environment} {plan_file}
   

   • If validation fails (exit code 1): STOP deployment, show errors
   • If validation passes (exit code 0): Continue to step 3
3. Check production safety confirmation requirement:
   • Configuration is loaded by sourcing cloud-common/scripts/config-loader.sh
   • config-loader.sh reads .fractary/plugins/faber-cloud/config.json
   • It sets DEVOPS_REQUIRE_CONFIRMATION from environments.{env}.require_confirmation
   • Example: If config has "prod": {"require_confirmation": true}, then DEVOPS_REQUIRE_CONFIRMATION="true"
   • If "true", mark that confirmation will be required after plan generation (step 9)
   • Continue to step 4
4. Run legacy validation (validate-plan.sh) for profile/backend checks
5. Validate AWS profile separation
6. Authenticate with AWS (via handler-hosting-aws)
7. Initialize Terraform and generate deployment plan
8. Review plan for safety
9. Execute production safety confirmation (if required):
   • If DEVOPS_REQUIRE_CONFIRMATION is "true" for this environment:

   bash plugins/faber-cloud/skills/cloud-common/scripts/production-safety-confirm.sh {environment} deploy {plan_summary_file}
   

   • If confirmation fails (exit code 1): STOP deployment, show abort message
   • If confirmation succeeds (exit code 0): Continue to step 10
   • If DEVOPS_REQUIRE_CONFIRMATION is "false" or not set: Skip confirmation, continue to step 10
10. Execute pre-deploy hooks:

bash plugins/faber-cloud/skills/cloud-common/scripts/execute-hooks.sh pre-deploy {environment} {terraform_dir}

• If hooks fail (exit code 1): STOP deployment, show error
• If hooks pass (exit code 0): Check for hook context and continue to step 11 10a. Load hook context (if available):
• Check for hook context files in /tmp/faber-cloud-hook-context-*.txt
• If found, read and apply the context for this deployment
• Prompt hooks may reference documentation, provide guidance, or include project-specific requirements
• Example:

  for context_file in /tmp/faber-cloud-hook-context-*.txt; do
    if [ -f "$context_file" ]; then
      echo "📋 Applying hook context from $context_file"
      cat "$context_file"
    fi
  done
  

11. Execute Terraform apply (via handler-iac-terraform), applying any context from step 10a
12. If permission error: Present error delegation options
13. Execute post-deploy hooks:

bash plugins/faber-cloud/skills/cloud-common/scripts/execute-hooks.sh post-deploy {environment} {terraform_dir}

• If hooks fail: WARN user, deployment already complete but post-deploy actions failed
• If hooks pass: Continue to step 14

14. Verify deployed resources (via handler-hosting-aws)
15. Update resource registry
16. Generate DEPLOYED.md documentation
17. Update deployment history
18. Report deployment results

OUTPUT COMPLETION MESSAGE:

✅ COMPLETED: Infrastructure Deployer
Environment: {environment}
Resources Deployed: {count}

Registry Updated: .fractary/plugins/faber-cloud/deployments/{env}/registry.json
Documentation: .fractary/plugins/faber-cloud/deployments/{env}/DEPLOYED.md
───────────────────────────────────────
View resources: /fractary-faber-cloud:infra-manage show-resources --env={environment}