5 ms·

hmm yes you are right, I've never thought of it this way actually. my thinking with Terrabook was like, what stops non-devops-savvy developers from starting to

hmm yes you are right, I've never thought of it this way actually. my thinking with Terrabook was like, what stops non-devops-savvy developers from starting to use TF? And the hypothesis is that it's a bunch of things that need to be set up prior to getting to something working, like a VPC and so on. And then having that, how do I get a database? The fastest way seems to be just find someone's github and copy from there, assuming I'm not familiar with the TF world. So I thought, why not build this right into the tool

verdverm 4y ago
The harder part for non-devops is not the TF side, but the cloud architecture and known best practices in design. After that the TF is pretty easy and mechanical Another point to consider is that most devs don't want yet another tool / SaaS to do a bit of bootstrapping. Also, the move towards exposing non-devops to devops without guidelines / constraints is ill-advised. So many cost / security issues to clean up after by the devops team
tedmiston 4y ago
> my thinking with Terrabook was like, what stops non-devops-savvy developers from starting to use TF? That they can provision using a GUI console without having to understand all of the underlying AWS components required behind the scenes for a common setup. I've seen a few takes at tools that attempt to "export your live infra to resources using standard providers in HCL files" but I haven't seen anything that's really good at that yet. Hmm...