I've arrived at the same conclusions with module development patterns and whether to use azapi or azurerm for deployments. the new features in v2 of azapi really open up resources that seemed to exotic to develop for in terraform. looking forward to your module patterns video.
I'd add it is easy to overlook azapi on the basis of how it behaved before, because it has evolved quite a lot from the early v1s to v2. Features, like replace triggers help bring the behaviour closer to the handcrafted AzureRM approach, the removal of jsonencode/decode, preflight, & schema validation simplifies the authoring, not to mention the ability to call a REST API authenticated with the Azure Resource Manager API is very powerful when needed.
This is really useful, I didn't realise about the retry on AzApi!
You’re welcome! I think it should be standard on every resource. Like a meta-property..
You had me at vnet peering re-sync ❤
Haha that’s awesome. It’s a great feature! Glad you liked it
I've arrived at the same conclusions with module development patterns and whether to use azapi or azurerm for deployments. the new features in v2 of azapi really open up resources that seemed to exotic to develop for in terraform. looking forward to your module patterns video.
Glad you liked it. More often then not azapi is the right choice for me.
I'd add it is easy to overlook azapi on the basis of how it behaved before, because it has evolved quite a lot from the early v1s to v2. Features, like replace triggers help bring the behaviour closer to the handcrafted AzureRM approach, the removal of jsonencode/decode, preflight, & schema validation simplifies the authoring, not to mention the ability to call a REST API authenticated with the Azure Resource Manager API is very powerful when needed.
Yeah I 💯 agree
Thank you very much for the explanation betweet. AzureRM and AzApi. But can you please give me the key benefits between AzApi and Bicep?