In the software development industry, we often say, “We deploy stuff.” But what exactly is that “stuff”? Behind each deployment lies a… Continue reading on ITNEXT […]
When managing Azure infrastructure with Terraform — or any Infrastructure-as-Code tool for that matter — one of the more frequent ClickOps… Continue reading on Medium »
In cloud automation, subtle missteps in identity management can lead to serious deployment challenges. One of the most common traps occurs… Continue reading on ITNEXT »
One of the most important (and overlooked) truths in infrastructure as code is this: Terraform is not application code.That might sound… Continue reading on DevOps.dev »
One of the most important (and overlooked) truths in infrastructure as code is this: Terraform is not application code.That might sound… Continue reading on Medium »
Naming every module in Azure Bicep used to be mandatory. With the release of the optional module names setting an explicit module deployment name is now optional. With […]
Over the years, working with Azure and various other cloud providers, I’ve seen — and made — my fair share of automation mistakes. These… Continue reading on Azure Terraformer »
In the ever-expanding universe of infrastructure as code, Terraform has become a starship of choice for cloud engineers. And when… Continue reading on Azure Terraformer »
Azure provides multiple ways to interact with and provision resources, each designed to suit different workflows and preferences. Whether… Continue reading on Azure Terraformer »