I recently purchased an Asus Zephyrus G15 (2021) laptop with a Ryzen 9 5900HS processor and RTX 3070 GPU. I really enjoy the light weight, relatively diminutive size and curiously long battery life of this machine which also packs a performance punch when needed. However, one thing I was not prepared for was Asus and their lackluster firmware/drivers/etc. for basic things like the keyboard. I don’t want to turn this into a long post because if you show up on this page you are probably just looking for the fix. So to keep it short… (more…)

Working with Terraform to build VM’s in Azure for proof-of-concept work, I often opt to use Ubuntu for my Linux systems. Up until 18.04 everything worked fine but when I tried to go to 20.04 or later my Terraform deployment would error out with:

Failure sending request: StatusCode=404 -- Original Error: Code="PlatformImageNotFound" Message="The platform image 'Canonical:UbuntuServer:20.04-lts:latest' is not available. Verify that all fields in the storage profile are correct.

Did Microsoft suddenly fall behind the curve with available OS images for one of the world’s most popular operating systems?

Thankfully, no. The answer is actually pretty simple… they just started breaking out different versions of the popular operating systems under different ‘offer’ families and your Terraform code needs to reflect as much.

Working with the cidrsubnets function in Terraform is a bit of a pain – but it’s so extremely handy for automated networking that it’s worth spending the time to figure it out. Suffice to say, I am not going to dig deep on how to use cidrsubnets; rather I am going to bring up a really handy and (as far as I can tell) “not documented” method for supplying a list of “newbits” values to this function.

If you thought the title of this article was just a bunch of mental word vomit, well, it kind of is. But the words all have meaning and I wanted to quickly talk about a key issue that I have continued to come across in my journey with Terraform… namely, getting things to apply consistently and successfully – particularly when introducing things to make end-use of your custom modules easier and your code more succinct and versatile – like conditionals and meta arguments such as “count” and “for_each”. (more…)