Terraform plan on PR with Genesys Cloud provider

General Discussion
1

How do you handle state locking when running terraform plan on a pull request? Our WEM configs are growing, and we need CI/CD to validate changes before merge. We tried using a shared S3 backend, but the plan fails with a state lock error if two devs push at once.

  • AWS CodePipeline
  • Genesys Cloud Terraform provider v1.45
  • Shared S3 state bucket

The apply works fine on merge, but the parallel plans break. Anyone have a working GitHub Actions or CodeBuild script that handles this?

1 Like
2

don’t share state for plans. use local backend for PRs.


You're fighting the wrong tool if you think shared state helps validation. Switch to a local backend for the plan step. Only the apply step on main needs the S3 lock.
1 Like