2 ms·
Oh man, was excited to try this but then was prompted to login. Why do I need to sign in with my GitHub? Why can’t I just generate terraform like you claim? Why
by gabereiser 4y ago
Oh man, was excited to try this but then was prompted to login. Why do I need to sign in with my GitHub? Why can’t I just generate terraform like you claim? Why do I have to give you personal details to do so?
- igorzij 4y agoFair point indeed. They way we built it is that it actually generates and applies Terraform in your AWS account and synchronises it with your Github. The idea is to eliminate all devops-y steps from the flow so that the user who knows nothing about AWS or Terraform can use it.
- gabereiser 4y agoI’m not the target audience then because I would never allow a service to just automatically update my AWS account infrastructure without allowing me to scrutinize the terraform first.
- skyzyx 4y agoI think that too much simplification without empowering people to understand how the pieces work is ultimately a detriment. It’s important that there is a human understands how the stuff works that’s getting shipped to production. You can’t skip that step, or who knows what kinds of vulnerabilities and miss configurations will end up going live. In my opinion, rather than building a tool for people who don’t understand the stuff, your target audience should change to instead be those who DO understand this stuff. This is not something that can be solved with automation-only if nobody understands how the pieces work.