James Bardin 31ca293777 fix slash handling around workspace_key_prefix ... The handling of slashes was broken around listing workspaces in workspace_key_prefix. While it worked in most places by splitting an extra time around the spurious slashes, it failed in the case that the prefix ended with a slash of its own. A test was temporarily added to verify that the backend works with the unusual keys, but rather than risking silent breakage around prefixes with trailing slashes, we also add validation to prevent users from entering keys with trailing slashes at all.		2019-02-22 10:29:10 -05:00
..
backend.go	fix slash handling around workspace_key_prefix	2019-02-22 10:29:10 -05:00
backend_state.go	fix slash handling around workspace_key_prefix	2019-02-22 10:29:10 -05:00
backend_test.go	fix test that never worked	2019-02-22 10:14:53 -05:00
client.go	backend/s3: Configure AWS Client MaxRetries and provide enhanced S3 NoSuchBucket error message	2019-01-09 13:01:37 -05:00
client_test.go	backend/remote-state: Get all the backend tests building again	2018-10-16 19:14:11 -07:00