Infrastructure as Code Landscape with Matt Gowie

In this episode, we dive into the evolving world of Infrastructure as Code (IaC) with a special guest, Matt Gowie, CEO of MasterPoint. Matt shares his expert insights on the current landscape of IaC, the latest trends, and the challenges companies face when adopting IaC strategies.
Whether you're an IT professional, DevOps enthusiast, or just curious about how code can manage infrastructure, this conversation is packed with valuable insights.
*Topics Covered:*
The evolution of Infrastructure as Code
Key tools and platforms shaping the IaC ecosystem
Common pitfalls in IaC adoption
How companies can improve infrastructure management with IaC
Enter the Terralith: masterpoint.io...
You can find Matt Gowie on LinkedIn: / gowiem
Or on Masterpoint: masterpoint.io/
#terraform #hashicorp #devops #cloudengineer #infrastructureascode
▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬
⭐ CONNECT WITH ME 🏃🦖
🌐 Day Two Cloud: daytwocloud.io
🌐 Chaos Lever: chaoslever.com
🌐 Visit my Website ► nedinthecloud.com
🗳 Pluralsight ► app.pluralsigh...
🐙 Find the code at GitHub► github.com/ned...
🐧 Twitter ► / ned1313
👨‍💼 LinkedIn► / ned-bellavance
For collaboration or any queries: [e-mail]
▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬
🌮 About Me 🌮
Ned is a curious human with a knack for creating entertaining and informative content. With over 20 years in the industry, Ned brings real-world experience to all his creative endeavours, whether that's pontificating on a podcast, delivering live instruction, writing certification guides, or producing technical training videos. He has been a helpdesk operator, systems administrator, cloud architect, and product manager. In his newest incarnation, Ned is the Founder of Ned in the Cloud LLC. As a one-man-tech juggernaut, he develops courses for Pluralsight, runs two podcasts (Day Two Cloud and Chaos Lever, and creates original content for technology vendors.
Ned has been a Microsoft MVP since 2017 and a HashiCorp Ambassador since 2020, and he holds a bunch of industry certifications that have no bearing on anything beyond his exceptional ability to take exams and pass them. When not in front of the camera, keyboard, and microphone, you can find Ned running the scenic trails of Pennsylvania or rocking out to live music in his hometown of Philadelphia. Ned has three guiding principles: Embrace discomfort, Fail often, and Be kind.

[@sudo-bandit]

great interview. i learned some stuff. i would love to hear matts view on security good practices.

[@quiet_nature397]

Yes, would love to know more about K8s

[@amglover4361]

I've written several Powershell 'wrapper' scripts that do a 'state list' then present that list as a PS grid from where you can choose one or more resources on which to perform various changes, eg remove from state+HCL, rename resources (does a state move and finds+replaces within the HCL) etc. Also, ones to find Azure resources that aren't TF'd and automagically import them. They've proven quite useful...

[@robc1775]

Came for the IaC, stayed for the goatee's!
I've been hired on several times now to un-eF a company's Terralith. Or when I started somewhere I discovered all their terraform was a Giant terralith and no one knew how to use it or understood it. And it can take quite a while to just understand it. They'll have modules on top of modules calling other modules that call even more modules. idk why some of these outside teams do such a thing to these companies. I don't feel bad for the Companies, I feel bad for me having to sort it out!

[@adamstirk]

I’d be interested in a video about breaking up a terralith, there were some valid points made that we are currently facing

[@NedintheCloud]

We've got something planned for later in the year. Stay tuned!

[@babunito]

Been thinking a lot about this 'terralith' thingy, and had this fear somewhere inside, that if using single state is really a good approach. Seems like it is not only me.
Would be fascinating to see a video, which would give some guidelines about criteria which could help to identify when to use terralith and when 'micro-terra'. Plan/apply time? Amount of resources? May be some types of resources should always have separate state, like AKS? Multi-region?
So far I was only thinking about plan/apply times - if it is quick enough - let it stay in one state, cause convenience of stitching everything in one root module is so hard to beat.

[@amglover4361]

Separate state candidate: Azure Application Gateway?! Any change which is made outside of TF seems to cause TF to want to redo everything (listeners, probes, rules etc etc). This is a constant annoyance. I guess it's probably not Hashicorp's fault - probably just how the API works....

[@NedintheCloud]

I haven't looked at the resource in the provider, but I'm guessing it could use some love. Lord knows the Azure Firewall is in a similar state.