3 ms·
The recommended way, at least for AWS, is to have multiple accounts. One for production, and then however many more for test and development. Separate accounts
by matwood 8y ago
The recommended way, at least for AWS, is to have multiple accounts. One for production, and then however many more for test and development. Separate accounts let you run TF changes and know you will not impact production.
TF can be tricky to grok at first especially if you don't have everything in TF. But, I couldn't imagine managing more than a server or 2 without it or something similar at this point. Once you get into VPCs, IAMs, etc..., some type of tool is really required.
I'm also a little confused about your transparency comment. IME, tf is very clear what it is going to do in a plan. The current state files are also just json, and easy to read/search if you're not sure about something.
- hinkley 8y agoDeclarative syntax is notoriously hard to debug, especially for newbies. As a general rule, if you're giving someone a tool that uses declarative syntax, you also need to provide them a private (not shared) sandbox in which to test out theories, try new things, and reproduce errors seen in production. Since we don't have that, TF is pretty much the worst solution for our problems. Kube or even Docker Swarm would serve us much better.