Idempotency and its importance

Idempotency means no matter how many times you run your pipeline or what the current state of your cloud resources is, you always get the same result at the end of your deployments.

Idempotency

For example, if your template is deploying a storage account in the first run, and then an additional storage account if you run it again, it is not idempotent. It is very important to keep your deployment idempotent to prevent any change in behavior, which makes troubleshooting a nightmare.

Immutability

Immutability is also something that you need to consider. Not only it is important to make sure your templates provide the same result at each run, but the configuration of your resources must be maintained if no change has been recorded.

These issues usually happen when you are not as confident about your cloud deployment as you are about your code and as such, your applications might suffer from slow memory, run out of disk space, and more. To...