3 ms·
Terraform. My god, just use terraform. Stop scripting random stuff to create multiple untracked resources in different places by hand. Slap this[1] on top of
by orf 5y ago
Terraform. My god, just use terraform.
Stop scripting random stuff to create multiple untracked resources in different places by hand.
Slap this[1] on top of this[2] and add whatever other services you want, and boom. Done.
1. https://stackoverflow.com/questions/49743220/how-do-i-create-an-ssh-key-in-terraform https://stackoverflow.com/questions/49743220/how-do-i-create...
2. https://registry.terraform.io/providers/1Password/onepassword/latest https://registry.terraform.io/providers/1Password/onepasswor...
- avisser 5y agoI think you're focused on the domain chosen by the author and not the more general technique. Replace the steps with "Releasing a build to my app store" or something else.
- scubbo 5y agoThis type of "helpfully-correcting disagreement" (rather than pointless-but-satisfying snark) is one reason why I greatly prefer Hacker News to almost-every other social network. Thank you!
- c7DJTLrn 5y agoYes, but I think you've been spoilt if every shop you've worked at already knows and uses Terraform. It's a real uphill battle to introduce it to a place where nobody has the mindset of treating computers as cattle, has never played around with declarative tools or config management before.
- iso1631 5y agoCongratulations, you've just made the situation worse by rushing to what you think a solution is, rather than seeing that the actual problem is.
- orf 5y agoThe problem is you’ve got a bunch of things that need to be in a particular state (for every employee, for every office, for every foo). There are a few solutions to this. Documentation with manual actions, a bunch of imperative code to create but not manage these things, or something that describes what you want without the “how I get it”. If you’re at the stage where you think writing a bunch of random Python code to prompt a user with steps is an acceptable solution then I can’t see how the situation can get much worse.
- iso1631 5y agoThe problem domain here involved getting a private key on a user's machine, and a public key in a location it can be pulled from to grant access. Your proposed solution, as correctly pointed out in stack overflow, is a security nightmare. > I should point out here that passing private keys around is generally a bad idea and you'd be much better having developers create their own key pairs and provide you with the public key that you (or them) can use to generate an AWS key pair
- orf 5y agoI mean, yes, but not really. They are clearly in a corporate environment and it wouldn't be unusual to say that the company needs access to your private keys you use to do work for said company. Just like they would have access to your laptop, and likely the disk encryption keys on it as well. Using 1Password as a middleman here is quite convenient - it's a secure encrypted way of transfering them to the user that is accessible to the company when/if they need it.