Terraform provider lock file

Hi all,

I have been a native terraform user for a long time and investigating how terraspace works with native terraform functionality.

Since terraspace init creates the terraform provider lock file along with the final terraform source in the cache directory, what is the best practise to maintain the lock file in scm?

I have only seen references to lock the module versions in the Terrafile.

Currently, no way. The way would probably handle in the future is to save the lockfile in a corresponding folder and “restore” it for each run. Hope that at least answers the question

Thanks @tung for clarifying. It makes sense to save the lock file and restore it for each run. Do we have a feature request for this that can be tracked?

Not yet. Feel free to open one

1 Like

created feature Add support for native terraform provider lock file · Issue #350 · boltops-tools/terraspace · GitHub