Because of veritical integration. Terraform will always be constrained by the fact that it's multi cloud. Microsoft can move fast to modify ARM template versions, ARM engine/backplane, and Bicep all at the same time. Terraform will always be playing catch up.
simple in terrform you maintain a state file , where as in bicep your portal is your state ., also terraform is terrible when it comes to import existing infra into code .....
Thanks John and Stephanie!
Neat explanation, thanks a lot!
every question is great... where did that came from its specific to US , i hear that a lot in my company... what a nightmare...
This was a fun video
Would be interesting to know why Microsoft decided to make bicep when we already have terraform
Aeomba hit was called.
Because of veritical integration. Terraform will always be constrained by the fact that it's multi cloud. Microsoft can move fast to modify ARM template versions, ARM engine/backplane, and Bicep all at the same time. Terraform will always be playing catch up.
simple in terrform you maintain a state file , where as in bicep your portal is your state ., also terraform is terrible when it comes to import existing infra into code .....
🎄🎇👋🏼🇨🇴🧔🏻👍🏼🤝🏼
nex video