All technologies
state backends
2 painsavg 8.5/10
config 1storage 1
Hardcoded backend configuration leads to destructive state file mismatches
9When copying root modules without updating backend configuration (key/prefix), Terraform can reference the wrong state file, resulting in destructive plans that delete infrastructure belonging to another environment or project.
configTerraformstate backends
Local state files without remote backends cause team collaboration and disaster recovery issues
8State files stored locally (default) instead of on remote backends (S3, GCS) prevent team collaboration, create single points of failure, and make disaster recovery impossible. Developers must manually manage state file access.
storageTerraformstate backendsS3