We should not append a "/" to the marker when returning list results in the case of directories (RELATIVE_PATH), as the names will already include the delimiter. Added a jclouds test to catch such regressions in the local store in the future.
Plumbs the prefix option to the openstack-swift provider. In the process, the support for the recursive option is modified to avoid setting the _path_ parameter, but rather use the delimiter if required (setting the delimiter is sufficient for a non-recursive listing).
Implements prefix support for the local blob store. The patch allows for correctly parsing prefixes that may not terminate with a delimiter (i.e. foo with delimiter "/" and a key foobar/key, should return foobar/ as the common path) and ones that do (i.e. foo/). NOTE: there is a small change in behavior in this patch. LocalBlobStore used to return the common prefixes without the delimiter character ("/"). However, other providers do include the delimiter (I checked S3 and Google Cloud Storage) and LocalBlobStore should include it as well.
jclouds should issue the requests to create all of the containers in the container pool before sleeping. The patch modifies the createContainerAndEnsureEmpty() method to take an additional parameter, which specifies whether awaitConsistency() should be called or not.
…er impl modify the BasicAuthenticator in Keystone destroy node if creation timeouts
refactor AccountApiExpectedTest to AccountApiMockTest refactor DatacenterApiExpectTest to DatacenterApiMockTest refactor SoftwareDescriptionApiExpectTest to SoftwareDescriptionApiMockTest refactor VirtualGuestApiExpectTest to VirtualGuestApiMockTest refactor VirtualGuestBlockDeviceTemplateGroupApiExpectTest to VirtualGuestBlockDeviceTemplateGroupApiMockTest
we now use segment conventions that allow us to do more efficient listing
When a filesystem blob does not have content metadata and when users set jclouds.filesystem.auto-detect-content-type to tru, probe the file type to return to clients. This is useful when using jclouds to serve an existing filesystem.
Currently swift creates blob-1, blob-2... blob-n for multipart upload segments, which are very common names that can easily collide with normal objects. This changes the naming convention to that of python-swiftclient (the `swift' command line). python-swiftclient also uses a different segment container by default, that's not implemented by this patch
Providers yield different messages so remove parsing from test. Also narrow exception handling scope.TTP 416 into IllegalArgumentException Providers yield different messages so remove parsing from test. Also narrow exception handling scope.