6 Commits

Author	SHA1	Message	Date
James Bardin	b279b1abb5	check for named s3 states before acquiring a lock ... In order to force-unlock a named state, we have to fetch that state first. Don't attempt to acquire a lock if we know the state already exists in s3.	2017-05-19 14:40:59 -04:00
James Bardin	9c431aee1b	only list environments when the keyName matches ... Prevent extra keys in the s3 envPrefix path from showing up as listed environments. Better handle keys containing slashes Add tests for unexpected keys in s3.	2017-04-12 13:57:22 -04:00
James Bardin	575e7f1811	Properly create a new named state in s3 ... If the state doesn't exist, we need to initialize one so that it can be listed be States.	2017-03-23 10:03:22 -04:00
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
James Bardin	4980fa20e7	move s3 config from client to backend ... The RemoteClient needs to be configured for the named state, so move the general config to the backend. Rename some fields for consistency.	2017-03-22 15:52:55 -04:00
James Bardin	9f5cf2b105	convert S3 remote state to a backend ... Move the S3 State from a legacy remote state to an official backend. This increases test coverage, uses a set schema for configuration, and will allow new backend features to be implemented for the S3 state, e.g. "environments".	2017-03-22 10:59:37 -04:00