Azure
There are two new pretty neat provider-defined functions with the new major release version of the Terraform AzureRM provider which I kind of missed initially but seem pretty cool to use. normalise_resource_id which tries to "normalise" the case-senitive segments of a resource ID in
Azure
You can apply precondition and postcondition blocks to your resources in Terraform if you want to assume some properties will be true/false before apply or if you want to guarantee some properties will be true/false after apply when supplying your modules to consumers. Rules for evaluating conditions When
Azure
When writing Terraform Modules that you intend to share with your team or customers so they can consume them and create infrastructure it is common that you will write some base code and accept some input variables. Input variables let you customize the modules to make the deployment fit the
Azure
Did you know that you can set up conditional deployments with Azure Bicep? Maybe the condition is that if this value is true = deploy the resource. It could also be if the var equals prod then deploy the resource into PROD or else deploy it into QA and use the
DevOps
We have on this website previously covered using scale set agents in Azure Devops for running your pipelines. They use Azure Virtual Machine Scale Set (VMSS) in the background and require you to configure this resource in the Azure Portal. This is beneficial if you want to make use of
If you have an Azure web application firewall (WAF) infront of your load balancer and this firewall has rulesets enabled with prevention mode set to Prevention instead of Detection you may see some requests not reaching your web application. It is recommended to first run your WAF in Detection mode
Azure
Ansible is automation everything IT If you have maybe 1-5 servers in your setup managing them individually should still be pretty easy. Now think about managing 200+ servers. If you had to login to them all individually that would just not be feasible. This is something we have dealt
Azure
The custom script extension is an extension you can apply on your virtual machine or virtual machine scale set that can download and execute scripts inside your operating system. This is beneficial if you have some post deployment tasks that you want achieved once the VM is deployed. For example
Azure
With Azure Devops you can use Microsoft hosted agents when configuring your pipelines. This means that all you need to focus on is configuring your pipeline and .yaml files. Once they are executed Microsoft takes care of the underlying compute that runs your code. The benefit of this is that
Azure
I have recently been working a lot with Azure Devops and setting up pipelines for a customer of mine. When doing this we decided to utilize the environments feature in Azure Devops which is a pretty neat tool. Whilst researching this I have recorded some insights which I will share
Azure
An issue with many getting started templates and tutorials for Azure Bicep is that everything is deployed into one single resource group, and afterwards destroyed with the same resource group. It is very simple for demos and guides to have it this way but once you move into the real
Terraform
In terraform we have something called a a lifecycle block. It is very useful for many reasons. In this post we will focus primarily on two which are prevent_destroy and ignore_changes I have a small configuration where I will create an SQL server and a database in Azure.