Terraform configuration files are source code and should be managed using a version-control system (VCS) such as Git. Using a VCS with established branching, push, and merge procedures provides proper history tracking, collaborative code review (via pull/merge requests), conflict resolution, and rollback capability — all essential for a growing team working on shared infrastructure code. Shared network folders, object storage bucket versioning, or synced Google Drive folders do not provide the branching, merging, and review workflows necessary for safe collaborative code changes, making them unsuitable substitutes for a proper VCS. This aligns with HashiCorp's and Google Cloud's recommended practices for managing Terraform configurations as code in a repository like Git.
Community Discussion