702413702c
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. |
||
|---|---|---|
| .. | ||
| testdata/test-config | ||
| config_snapshot.go | ||
| config_snapshot_test.go | ||
| doc.go | ||
| planfile_test.go | ||
| reader.go | ||
| tfplan.go | ||
| tfplan_test.go | ||
| writer.go | ||