James Bardin 3cf84bb3f9 don't add state to the validate context ... The validate command should work with the configuration, but when validate was run at the start of a plan or apply command the state was inserted in preparation for the next walk. This could lead to errors when the resource schemas had changes and the state could not be upgraded or decoded.		2020-08-07 14:13:57 -04:00
..
atlas	backend/atlas: fix use of T.Fatal() inside goroutine	2019-11-06 17:11:15 -08:00
init	Add kubernetes backend	2020-06-04 02:29:57 -04:00
local	don't add state to the validate context	2020-08-07 14:13:57 -04:00
remote	Revert "backend/local: release lock if there is an error in Context() (#25427)"	2020-06-30 14:12:32 -04:00
remote-state	Azure backend: support snapshots/versioning (#24069)	2020-06-25 11:50:16 +02:00
backend.go	backend: Allow certain commands to opt out of required variable checks	2019-10-10 10:07:01 -07:00
cli.go	backend: Update interface and implementations for new config loader	2018-10-16 18:39:12 -07:00
nil.go	Change backend.ValidateConfig to PrepareConfig	2019-02-25 18:37:20 -05:00
nil_test.go	backend: introduce the backend set of interfaces	2017-01-26 14:33:49 -08:00
operation_type.go	Version tools per Go convention under tools.go	2019-10-17 22:23:39 +02:00
operationtype_string.go	stringer: Regenerate files with latest version	2019-05-13 15:34:27 +01:00
testing.go	finish provider ModuleInstance replacement	2020-03-11 14:19:52 -04:00
unparsed_value.go	Avoid leaking sensitive values in undeclared warnings	2019-11-05 17:32:57 -08:00
unparsed_value_test.go	backend/local: Handle interactive prompts for variables in UI layer	2019-10-10 10:07:01 -07:00