Question

Your platform team manages infrastructure across Google Cloud and AWS using a single Terraform codebase. You want to bootstrap the tooling so that GCP and AWS resources can be provisioned and destroyed independently, while sharing common module definitions and enabling parallel CI/CD runs without one cloud's failures blocking the other. What is the recommended approach to structure the Terraform configuration?

Accepted Answer

Create separate root configurations (each with its own backend/state) per cloud, referencing shared reusable modules from a versioned module source.

Answer

Place both providers in a single root module with one shared state file, and use provider aliases to distinguish GCP and AWS resources.

Answer

Use a single root configuration but rely on the -target flag in CI to apply only GCP or AWS resources on each run.

Answer

Store all resources in one workspace and use conditional count expressions to toggle which cloud's resources are created per apply.