> @@ -121,4 +124,13 @@ public AWSS3AsyncBlobStore(BlobStoreContext context,
> BlobUtils blobUtils,
> blob2Object.apply(blob), options);
> }
>
> + @Override
> + public ListenableFuture<Boolean> createContainerInLocation(Location
> location, String container,
> +
> CreateContainerOptions options) {
> + if (Futures.getUnchecked(containerExists(container))) {
> + // Return false if container already exists. See JCLOUDS-334 for
> details.
> + return Futures.immediateFuture(Boolean.FALSE);
> + }
> + return super.createContainerInLocation(location, container, options);
> + }
Any reason not to put this in `S3AsyncBlobStore`? I know you mentioned that
this _does_ work as intended for generic S3 providers...is that because other
S3-compatible blobstores implement `putBucketInRegion` (which seems to be the
[actual call
made](https://github.com/jclouds/jclouds/blob/master/apis/s3/src/main/java/org/jclouds/s3/blobstore/S3AsyncBlobStore.java#L271))
differently?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/173/files#r6882659
