Martin Atkins 0009768c7f internal/depsfile: Update the dependency lock file atomically ... In this case, "atomic" means that there will be no situation where the file contains only part of the newContent data, and therefore other software monitoring the file for changes (using a mechanism like inotify) won't encounter a truncated file. It does _not_ mean that there can't be existing filehandles open against the old version of the file. On Windows systems the write will fail in that case, but on Unix systems the write will typically succeed but leave the existing filehandles still pointing at the old version of the file. They'll need to reopen the file in order to see the new content.		2020-10-14 08:01:19 -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: Update the dependency lock file atomically	2020-10-14 08:01:19 -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