terraform/internal/depsfile
Martin Atkins 773dd56b42 internal/depsfile: Introduce the concept of "non-lockable" providers
It doesn't make sense for a built-in provider to appear in a lock file
because built-in providers have no version independent of the version of
Terraform they are compiled into.

We also exclude legacy providers here, because they were supported only
as a transitional aid to enable the Terraform 0.13 upgrade process and
are not intended for explicit selection.

The provider installer will, once it's updated to understand dependency
locking, use this concept to decide which subset of its selections to
record in the dependency lock file for reference for future installation
requests.
2020-09-08 09:50:58 -07:00
..
testdata/locks-files internal/depsfile: Introduce the concept of "non-lockable" providers 2020-09-08 09:50:58 -07:00
doc.go internal/depsfile: Loading locks from HCL files on disk 2020-09-08 09:50:58 -07:00
locks.go internal/depsfile: Introduce the concept of "non-lockable" providers 2020-09-08 09:50:58 -07:00
locks_file.go internal/depsfile: Introduce the concept of "non-lockable" providers 2020-09-08 09:50:58 -07:00
locks_file_test.go internal/depsfile: SaveLocksToFile implementation 2020-09-08 09:50:58 -07:00
paths.go internal/depsfile: Loading locks from HCL files on disk 2020-09-08 09:50:58 -07:00