@shcallaway: I am compulsively Terraforming EVERYTHING at Sazabi. - Google Workspace users, groups, perms - Google Drives - 1Passwor…

I am compulsively Terraforming EVERYTHING at Sazabi. - Google Workspace users, groups, perms - Google Drives - 1Password vaults and items - Mercury virtual cards Soon we will Terraform Slack channels and Rippling configuration. I'm having a hard time explaining why I need to do this, but any infra engineer who has tried managing multiple shared AWS accounts will understand... All of this is company state. Codifying state in files gives me the ability to check them into git, which in turn provides version control and audit-ability. Files are also convenient for agents. It's way easier for my agent to manipulate Google Workspace through files vs. whatever god-forsaken programmatic interfaces it offers. Terraform serves as a single source of truth, so I can easily identify when a certain configuration has been bent out of shape and correct it (this happens frequently with agents). Sure, merging a PR and running `tf apply` to create a new Slack channel may seem like overkill - but the benefits far outweigh the costs. Don't judge me.