3 ms·
I don't understand the problem. Use something like `terraform plan` as a comment on the pull request and manually look over the changes before pulling in.
by whimsicalism 5y ago
I don't understand the problem. Use something like `terraform plan` as a comment on the pull request and manually look over the changes before pulling in.
- spondyl 5y agoI don't use Terraform but I think you're describing something like Atlantis? https://www.runatlantis.io/ https://www.runatlantis.io/ I remember seeing a team running this at a previous company I worked at
- a012 5y agoAtlantis is just like the GP's mentioned: a CI to run terraform plan then a person needs to examine the dryrun output. But it's still not ideal because Atlantis also has persmissions on production, and a (human) mistake could brought down your infrastucture.
- rmetzler 5y agoThere is also documentation on how to integrate Terraform with Gitlab Merge Requests https://docs.gitlab.com/ee/user/infrastructure/mr_integration.html https://docs.gitlab.com/ee/user/infrastructure/mr_integratio...
- viraptor 5y agoNot even before pulling in - the state may change in between the comment and the applying. A safer way is to dump the plan from after the merge and not apply that specific plan until after it's manually approved.
- sontek 5y agoYeah, terraform cloud from hashicorp does this