Martin Atkins 264a3cf031 depsfile: Flatten the "hashes" locks to a single set of strings ... Although origin registries return specific [filename, hash] pairs, our various different installation methods can't produce a structured mapping from platform to hash without breaking changes. Therefore, as a compromise, we'll continue to do platform-specific checks against upstream data in the cases where that's possible (installation from origin registry or network mirror) but we'll treat the lock file as just a flat set of equally-valid hashes, at least one of which must match after we've completed whatever checks we've made against the upstream-provided checksums/signatures. This includes only the minimal internal/getproviders updates required to make this compile. A subsequent commit will update that package to actually support the idea of verifying against multiple hashes.		2020-09-24 14:01:54 -07:00
..
empty.hcl	internal/depsfile: Loading locks from HCL files on disk	2020-09-08 09:50:58 -07:00
invalid-provider-addrs.hcl	internal/depsfile: Introduce the concept of "non-lockable" providers	2020-09-08 09:50:58 -07:00
invalid-versions.hcl	depsfile: Flatten the "hashes" locks to a single set of strings	2020-09-24 14:01:54 -07:00
unsupported-block.hcl	internal/depsfile: Loading locks from HCL files on disk	2020-09-08 09:50:58 -07:00
valid-provider-locks.hcl	depsfile: Flatten the "hashes" locks to a single set of strings	2020-09-24 14:01:54 -07:00