2 ms·
I would tend to disagree. First, because not everyone is on AWS. Second, because even for people on AWS, some of a company's infra isn't on AWS (e.g. gmail). T
by pyrale 5y ago
I would tend to disagree.
First, because not everyone is on AWS.
Second, because even for people on AWS, some of a company's infra isn't on AWS (e.g. gmail).
Third because not every infra setup work has an AWS tool.
To take a personal example, we use multiple infra providers.
Some of our infra is gmail (currently working on automating it with terraform).
Some of it is other infrastructure providers that aren't US-based.
etc.
- sokoloff 5y agoWhat’s the “automating gmail with terraform” angle? G-suite automation? Or GCP?
- pyrale 5y agog-suite.
- europa 5y agoCan you elaborate on the terraform automation for gmail?
- pyrale 5y agoWhen we first built our user account system, we had to create a google user and add it to relevant groups in admin console whenever we hired someone, before the automation could kick in. We're tired of that so we're looking into using a terraform provider [1], so that we can declare new users and instantiate their resources with a simple PR. [1]: https://registry.terraform.io/providers/hashicorp/googleworkspace/latest/docs https://registry.terraform.io/providers/hashicorp/googlework...