You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Martin Atkins 702413702c plans/planfile: Include dependency locks in saved plan files ... We recently removed the legacy way we used to track the SHA256 hashes of individual provider executables as part of a plans.Plan, because these days we want to track the checksums of entire provider packages rather than just the executable. In order to achieve that new goal, we can save a copy of the dependency lock information inside the plan file. This follows our existing precedent of using exactly the same serialization formats we'd normally use for this information, and thus we can reuse the existing models and serializers and be confident we won't lose any detail in the round-trip. As of this commit there's not yet anything actually making use of this mechanism. In a subsequent commit we'll teach the main callers that write and read plan files to include and expect (respectively) dependency information, verifying that the available providers still match by the time we're applying the plan.		5 years ago
..
testdata/test-config	Move plans/ to internal/plans/	5 years ago
config_snapshot.go	Move plans/ to internal/plans/	5 years ago
config_snapshot_test.go	Move plans/ to internal/plans/	5 years ago
doc.go	Move plans/ to internal/plans/	5 years ago
planfile_test.go	plans/planfile: Include dependency locks in saved plan files	5 years ago
reader.go	plans/planfile: Include dependency locks in saved plan files	5 years ago
tfplan.go	core: Simplify and centralize plugin availability checks	5 years ago
tfplan_test.go	core: Simplify and centralize plugin availability checks	5 years ago
writer.go	plans/planfile: Include dependency locks in saved plan files	5 years ago