diff options
| -rw-r--r-- | doc/bugs/Support_non-default_storage_classes_with_Google_Cloud_Storage/comment_3_18aeaeace47224ad1c2c86beb356ddcb._comment | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/doc/bugs/Support_non-default_storage_classes_with_Google_Cloud_Storage/comment_3_18aeaeace47224ad1c2c86beb356ddcb._comment b/doc/bugs/Support_non-default_storage_classes_with_Google_Cloud_Storage/comment_3_18aeaeace47224ad1c2c86beb356ddcb._comment new file mode 100644 index 000000000..25cc4958f --- /dev/null +++ b/doc/bugs/Support_non-default_storage_classes_with_Google_Cloud_Storage/comment_3_18aeaeace47224ad1c2c86beb356ddcb._comment @@ -0,0 +1,11 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 3""" + date="2015-10-15T19:47:20Z" + content=""" +Your log shows it's passing x-amz-storage-class:NEARLINE in the object PUT +request, so at least that works. + +I've filed a bug on aws to get PutBucket extended to allow specifying a +StorageClass: <https://github.com/aristidb/aws/issues/182> +"""]] |