Before we used the previous container name, which kept appending and hit S3 limits during integration tests like:
Caused by: java.lang.IllegalArgumentException: Object 'gaul-blobstore27-4348532805015069992-1155797412711190448-1465016400636204031' doesn't match S3 bucket virtual host naming convention. Reason: Can't be null or empty. Length must be 3 to 63 symbols.. For more info, please refer to http://docs.amazonwebservices.com/AmazonS3/latest/index.html?BucketRestrictions.html You can merge this Pull Request by running: git pull https://github.com/maginatics/jclouds allocate-new-container Or you can view, comment on it, or merge it online at: https://github.com/jclouds/jclouds/pull/128 -- Commit Summary -- * Allocate new container name using prefix -- File Changes -- M blobstore/src/test/java/org/jclouds/blobstore/integration/internal/BaseBlobStoreIntegrationTest.java (2) -- Patch Links -- https://github.com/jclouds/jclouds/pull/128.patch https://github.com/jclouds/jclouds/pull/128.diff
