terraform/internal/depsfile
Martin Atkins e1cf0ac801 internal/depsfile: Control how the "hashes" value is formatted
Previously we were just letting hclwrite do its default formatting
behavior here. The current behavior there isn't ideal anyway -- it puts
big data structures all on one line -- but even ignoring that our goal
for this file format is to keep things in a highly-normalized shape so
that diffs against the file are clear and easy to read.

With that in mind, here we directly control how we write that value into
the file, which means that later changes to hclwrite's list/set
presentation won't affect it, regardless of what form they take.
2020-10-09 09:26:23 -07:00
..
testdata/locks-files depsfile: Flatten the "hashes" locks to a single set of strings 2020-09-24 14:01:54 -07:00
doc.go internal/depsfile: Loading locks from HCL files on disk 2020-09-08 09:50:58 -07:00
locks.go command/init: Read, respect, and update provider dependency locks 2020-10-09 09:26:23 -07:00
locks_file.go internal/depsfile: Control how the "hashes" value is formatted 2020-10-09 09:26:23 -07:00
locks_file_test.go internal/depsfile: Control how the "hashes" value is formatted 2020-10-09 09:26:23 -07:00
locks_test.go depsfile: Locks.Equal and Locks.Empty methods 2020-10-09 09:26:23 -07:00
paths.go internal/depsfile: Loading locks from HCL files on disk 2020-09-08 09:50:58 -07:00
testing.go command/init: Read, respect, and update provider dependency locks 2020-10-09 09:26:23 -07:00