senior-devops

Run the pipeline generator script with your project path, platform, and desired stages, for example python scripts/pipeline_generator.py ./app --platform=github --stages=build,test,deploy. It detects Node.js, Python, or Go projects and writes a workflow file to .github/workflows/ci.yml.

Use the terraform scaffolder with --provider=aws --module=ecs-service targeting your infrastructure directory. It writes main.tf, variables.tf, outputs.tf, and versions.tf, and runs terraform fmt and validate automatically when the terraform binary is installed.

Blue-green deploys to a separate slot and switches service traffic only after health checks pass, enabling instant rollback by switching the selector back. Rolling updates replace pods incrementally in place, which is simpler but mixes versions during the rollout.

No. The deployment manager only writes manifest files and prints an ordered runbook of kubectl commands. A human reviews and executes each step, so no change reaches the cluster without explicit approval.

It supports three provider-module pairs: AWS with ecs-service, GCP with gke-deployment, and Azure with aks-service. Each pair is validated, so requesting a mismatched provider and module returns an error listing the valid combinations.

Terraform or OpenTofu is the default choice for multi-cloud teams since one HCL language covers AWS, Azure, GCP, and thousands of providers. Choose Pulumi if your team prefers TypeScript or Python, and cloud-native tools like CloudFormation or Bicep only for single-cloud shops needing provider-specific features.