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
..
consul	cleanup consul lock entries	2017-04-06 14:19:55 -04:00
inmem	update remote-state/inmem client	2017-02-28 16:35:45 -05:00
s3	check for nil state in s3 client Get	2017-05-30 14:36:13 -04:00
backend.go	update remote-state.Backend	2017-02-28 16:35:45 -05:00
backend_test.go	backend/remote-state	2017-01-26 14:33:49 -08:00
testing.go	Move TestRemoteLocks to state/remote	2017-02-08 11:25:52 -05:00