Question

After running 'terraform init' in a new project directory, a developer inspects the working directory and notices a hidden '.terraform' subdirectory has been created. A teammate asks what should be done with this directory when committing the project to the shared Git repository. What is the correct guidance regarding the '.terraform' directory?

Accepted Answer

It contains the downloaded provider plugins and modules and should be excluded from version control via .gitignore.

Answer

It contains the dependency lock file and must always be committed to ensure consistent provider versions.

Answer

It stores the Terraform state file and should be committed so teammates share the same state.

Answer

It holds the provider version constraints defined in the configuration and must be committed for reproducibility.