Infrastructure as Code Landscape with Matt Gowie

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!

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...

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.

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

Yes, would love to know more about K8s

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