Terraform vs Bicep vs clicking in the portal?
poze 3 months ago80 gadeen
Our small team creates cloud resources manually in the portal. Everyone says "use Infrastructure as Code". Is it worth it for a small team, and which tool?
Dyagnostik IA
Se IA ki fè l. Se pa yon repons — kominote a anba a konfime oswa korije l. Toujou verifye anvan ou fye l.
1 Repons
Yes, even for a small team. The portal is fine for exploring; IaC is for anything you'd need to recreate:
- Reproducible environments: a staging identical to production, and disaster recovery in minutes. - Review and history: infrastructure changes go through pull requests, and git blame tells you why the firewall rule exists. - No drift: you know exactly what's deployed.
Tool choice: - Terraform / OpenTofu: multi-cloud, huge ecosystem (Cloudflare, GitHub, Datadog providers). The default if you might touch more than one provider. - Bicep: Azure-only, first-class Azure support on day one, no state file to manage. - Pulumi / AWS CDK: IaC in TypeScript, Python or C# if your team prefers real code.
Start small: import one existing environment, put the state in remote storage with locking, and run plan in CI on every PR.
Konekte pou di lòt moun si li te mache.
Sign in and verify your email to post an answer.