25e1c83 created the issue
Hi there,
This issue arose as a result of the fix introduced to #11062. While the "interoperability failure" issue was fixed previously, Cyberduck will now no longer honour the default storage class setting and will always upload files with storage class "Standard". As my storage bucket is using the "Archive" storage class (which, incidentally, does not appear to be supported by Cyberduck at the current moment in the "Info" tab), I have to change them manually using gsutils after each upload.
I wonder whether if it is possible to avoid specifying the "storageClass" parameter altogether, as per what itspage suggested, such that the file will upload only to the default storage class setting? I note that in versions 7.3.0 and before, there was no interoperability failure issue and the default storage class setting was honoured. Just wondering if it could be possible to revert to those settings back then.
Hi there,
This issue arose as a result of the fix introduced to #11062. While the "interoperability failure" issue was fixed previously, Cyberduck will now no longer honour the default storage class setting and will always upload files with storage class "Standard". As my storage bucket is using the "Archive" storage class (which, incidentally, does not appear to be supported by Cyberduck at the current moment in the "Info" tab), I have to change them manually using gsutils after each upload.
I wonder whether if it is possible to avoid specifying the "storageClass" parameter altogether, as per what itspage suggested, such that the file will upload only to the default storage class setting? I note that in versions 7.3.0 and before, there was no interoperability failure issue and the default storage class setting was honoured. Just wondering if it could be possible to revert to those settings back then.