Back in 2017 I wrote about recovering orphaned Terraform state with the import command. That post is still up because the situation is still the same: somebody created infra without managing state, somebody else has to bring it back under control, and you’re the somebody else. What’s changed is the tooling. Three things, mostly. ...
Yes. I upgraded to Catalina on the first day. ¯\_(ツ)_/¯ Now I’m trying to run a Python program and it’s exiting with Abort trap: 6. The crash report indicates the specific problem is with an OpenSSL dylib file… ...
This was written in 2017 when terraform import was the only option. The toolkit looks different now; see Recovering Terraform State, Eight Years Later for what I’d do today. Here’s the scenario… you have documented the steps for creating new infrastructure using Terraform including ensuring that state files are dealt with properly (remote in AWS S3). However, at some point those directions aren’t followed and you now have infrastructure that is orphaned with no state. What do you do? ...
Does the internet need another tech blog? No, probably not. However, I frequently lament doing a poor job documenting all the things I’ve figured out how to do over the years. Thus, I plan to make an effort to document those things here for all who find my methods sane to freely copy. ...