Folder placeholder objects should be set to standard storage class regardless of preference

[cyberduck]

0b3458e created the issue

I am looking to use Cyberduck with client-side encryption and Amazon S3 Glacier Deep Archive. When the S3 Default Storage Class preference is set to Glacier Deep Archive, folder metadata is also stored in that way? This is a problem.

1. Cannot upload to folders (cannot read folder meta)
2. Can upload a folder structure to root, but cannot
   i. open it
   ii. call Restore on it (=> cannot restore any contents)

If there was another Default Storage Class preference for folders or another hardcoded default it would be very helpful. For my use case of uploading pictures, I cannot use a flat structure + multiple buckets. Additionally, the flow used to produce 2. should probably be disallowed.

For completeness, there is a workaround:

1. Change the preference to Standard
2. Create folder(s)
3. Change the preference to Glacier
4. Upload file(s)

I have marked this as a bug because it represents a break from expectations.

[cyberduck]

0b3458e commented

To add to this, masterkey.cryptomator is also allowed to be a Glacier object (I think this also breaks things). It is created using Action > New Encrypted Vault.

[cyberduck]

@dkocher commented

Relates to #10488.

[cyberduck]

@ylangisc commented

In 6178de6.