3 ms·

I am a big fan of Azure ARM/Bicep. I can’t imagine needing to deal with stateful IaC. Perhaps Azure doesn’t need to do that because it’s able to provide guarant

I am a big fan of Azure ARM/Bicep. I can’t imagine needing to deal with stateful IaC. Perhaps Azure doesn’t need to do that because it’s able to provide guarantees about their own platform or something. The actual infrastructure and its configuration is the state. It does a diff to see what needs changing.

giaour 4y ago
Azure has some pretty strict internal requirements around resource creation that make this possible. Every service must provide a "Resource Provider"[0] API that supports idempotent creation operations and standardized query patterns for read operations. Whether you create a resource through an ARM template, in the portal, or via the CLI, it's going through the same unified API surface. So, there is definitely still state, it's just stored centrally. [0]: https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/resource-providers-and-types https://docs.microsoft.com/en-us/azure/azure-resource-manage...