If you’ve been following my recent posts on agentic DevOps, you know I’m a big believer in letting AI handle the repetitive parts of infrastructure reviews. But here’s the thing - most teams are still doing manual PR reviews for Bicep (and Terraform) files, catching the same anti-patterns over and over: “Hey, you forgot to enable HTTPS-only on that storage account.” “This VM SKU is way oversized for a dev environment.” “Did you check if this violates our naming conventions?”
Over the last few months, I’ve been working on an exciting project for our Microsoft Technical Trainer team, known as “Trainer-Demo-Deploy”, a catalog of Azure end-to-end demo scenarios, available as an Open-Source project.
While we managed to get about 50 templates live, there can never be enough scenarios to integrate into your Azure classes or POC activities if you ask me. One of the challenging tasks in the project is not only coming up with demo ideas, but also creating the actual artifacts, such as Azure templates with Bicep, sample apps and sample data.
Hey,
I got some GREAT NEWS to share, based on an email I received earlier this week:
which informed me I am recognized as a HashiCorp Ambassador!!
I can imagine that some of you might not be familiar with this recognition. Easy said, it is much like the Microsoft MVP title, rewarding individuals for their outstanding contributions in the technical communities.
In my personal case, my first adventures with Terraform started about 5 years ago. I was struggling with Azure ARM templates, and Terraform seemed like an easier language to achieve the same purpose, deploying Azure resources.
Hey everyone,
Thanks for joining the Azure Spring Clean online event again, in which the Azure community steps up once more, sharing the best tips & tricks on how to keep your Azure environments clean. Discussing optimizations, covering new services and features or overall giving you a view on how to manage your Azure subscriptions even better.
You can check out all other blog posts or videos, which can guide you with best practices, lessons learned, or help you with some of the more difficult Azure Management topics at Azure Spring Clean.
Hi all,
Earlier this week, I got blown away by an interesting Terraform issue.
The Problem Running a deployment that ran fine for months. I initiated a new deployment using the usual “terraform init” step, which ran fine. Followed by the usual “terraform plan”, and BOOM, the following message appeared:
Panic: not a collection type
Since this was a new template I created, I assumed an issue with the syntax or anything similar. As I couldn’t find anything, I tried running the same steps with a “valid” template. Only to find out it produced the same error message.
Cookie Consent
We use cookies to enhance your browsing experience and analyze site traffic.
Cookie Preferences
These cookies are required for the website to function and cannot be disabled.
These cookies help us understand how visitors interact with our website.
These cookies enable features like comments and embedded content.