James Bardin e7502454b4 check for nil state in s3 client Get ... The S3 client can return (nil, nil) when the remote state doesn't exist. The caused a nil pointer dereference when checking the payload.MD5 against the expected value. This can happen if the remote state was manually removed, but the digest entry was left in the DynamoDB table.		2017-05-30 14:36:13 -04:00
..
atlas	backend/atlas: accept ATLAS_ADDRESS env var for address	2017-03-16 23:04:07 -07:00
init	convert S3 remote state to a backend	2017-03-22 10:59:37 -04:00
legacy	Make backcend/legacy match new Backend iface	2017-02-28 16:35:45 -05:00
local	check for empty diff in CountHook.PreApply	2017-05-26 15:04:56 -04:00
remote-state	check for nil state in s3 client Get	2017-05-30 14:36:13 -04:00
backend.go	provide contexts to clistate.Lock calls	2017-04-01 17:09:20 -04:00
cli.go	command: use backend.CLIIinit	2017-02-28 10:58:29 -08:00
nil.go	Update Backend interface to latest iteration	2017-02-28 16:07:07 -05:00
nil_test.go	backend: introduce the backend set of interfaces	2017-01-26 14:33:49 -08:00
operation_type.go	backend: introduce the backend set of interfaces	2017-01-26 14:33:49 -08:00
operationtype_string.go	Restore stringer-generated files back to new version	2017-04-21 14:49:18 -07:00
testing.go	test for proper state persistence	2017-03-23 10:06:07 -04:00