James Bardin fa4dc01cf4 add named state support to the s3 backend ... This adds named state (environment) support to the S3 backend. A state NAME will prepend the configured s3 key with `env:/NAME/`. The default state will remain rooted in the bucket for backwards compatibility. Locks in DynamoDB use the S3 key as the as the primary key value, so locking will work as expected for multiple states.		2017-03-22 16:59: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	command: remove legacy remote state on migration	2017-03-20 10:14:59 -07:00
remote-state	add named state support to the s3 backend	2017-03-22 16:59:13 -04:00
backend.go	command: initial work on migrating envs, basic cases first	2017-03-01 10:59:17 -08: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	backend: introduce the backend set of interfaces	2017-01-26 14:33:49 -08:00
testing.go	Merge pull request #12558 from hashicorp/f-backend-testing	2017-03-15 08:45:20 -07:00