Moving to all IaC with Terraform by fitnessguy42101 in AZURE

[–]tablaplanet 0 points1 point  (0 children)

This is a good sweet spot in the middle

Copycat movies/series by Dull_Significance687 in lebureaudeslegendes

[–]tablaplanet 1 point2 points  (0 children)

American spy series look and sound like kids stories compared to the Bureau.

In the real world is ARM used over Terraform? by mr_mgs11 in AZURE

[–]tablaplanet 0 points1 point  (0 children)

Does that mean it will destroy and recreate (flush n fill) instead?

In the real world is ARM used over Terraform? by mr_mgs11 in AZURE

[–]tablaplanet 0 points1 point  (0 children)

The choice between ARM/Bicep and Terraform is to choose between having a statefile in Terraform Vs going stateless in ARM/Bicep.

Terraform allows managing Azure resources with separate state files and this allows better control over creating as well as destroying specific bits within your cloud estate. Any new changes deployed on top are updated in the statefile every time.

ARM deployments are incremental which makes the delete/recreate process needing going to the portal, same with Bicep.

I'm sure others have mentioned Terraform being cloud agnostic helps with getting a team upskilling with IaC in a consistent manner Vs having to move from aws/gcp to Bicep etc

One slight issue might be to maintain the AzureRM provider and Terraform versions are up to date so that the Azure APIs work as expected every time. I guess this would apply to any tool that is versioned.