Terraform state files can contain sensitive data, here’s how you can store them securely in Azure
Did you know you can reference custom Terraform modules direct from Git? Here’s how to do it, and how to make this work with an Azure DevOps pipeline
Deploying ARM Tempaltes with Terraform - don’t do it if you can avoid it, but if you have to here’s how.
How to debug Terraform Azure CLI commands by using Fiddler
How to deploy to multiple Azure subscriptions in your Terraform templates
Using a new VS Code extension to bring together Terraform, VS Code, Azure Cloud Shell and optimize the Terraform development experience
Earlier this month at Build Microsoft announced a new feature for ARM templates, the Terraform Resource Provider. If you’re not familiar with Terraform, it’s a way to define cloud infrastructure declaratively much like ARM templates, but one of its big benefits is that it works across cloud providers. If you’re interested in learning more about Terraform in Azure then take a look at my comparison of Terraform vs ARM templates. I’ve had access to the preview of this new feature for ARM templates and wanted to share my experience.
If you’ve been to any cloud or devops conference or meetup in the last year, you’ve probably heard about Terraform, the Infrastructure as Code tool from Hashicorp, it’s been one of the big talking points of the devops community for some time now. Terraform is a proprietary language for creating infrastructure as code deployment solutions, and one of it’s biggest selling points is that it supports multiple different cloud vendors including Azure.