4 ms·
Or you can give people enough permissions to plan but not apply and leave applying to a restricted set of users...
by jolux 3y ago
Or you can give people enough permissions to plan but not apply and leave applying to a restricted set of users...
- quickthrower2 3y agoAlso you can have laboratory cloud subscriptions seperate from production, where devs have full permissions.
- nijave 3y agoThat's tricky since the state file frequently contains secrets. You can try to keep secrets out of the state file but that's largely provider/resource dependent. For instance, if you create an AWS RDS Postgres database, the state ends up containing the resource password. If you allow only plans, users can still access the password in the state file.
- joombaga 3y agoFor RDS you can change the password after creating the DB, or use the SecretsManager integration. There are similar workarounds for other providers and resources. I use TF without storing secrets in the state file (providers: AWS, kubernetes, helm, onepassword, datadog, auth0, and more).
- macca321 3y agoYou can exfiltrate secrets that aren't in the state, but are in accessible resources during a plan using an http data source with the secret encoded into the url