Steps to reproduce.
Connect to a project with GCS protocol.
Right click on a bucket and select Info.
Lifecycle section shows "Transition to Glacier" = "after 1 day".
There is not a Glacier tier in GSC and there is no transition lifecycle rule in the bucket.
Bucket has Delete after 30 days configured but this does not show in the GUI.
Lifecycle rules have a lot more options that what is presented in the Cyberduck GUI. The rule that Cyberduck creates to delete objects isn't really correct since it sets the condition to be "Live", hence in a versioned bucket the object will never be deleted.
The GUI should have all the options to be complete, or at least if not all the options are supported it should work correctly for the options that are shown. e.g. The Delete object rule has 9 different conditions but only 1 is show in the GUI, but in the back end you are implementing 2 (age and live status"). Due to what is in the back end being different to what is in the GUI it causes it not to display correctly in the GUI. e.g. If you enter a Lifecycle rule for delete files after X days Cyberduck doesn't display this rule in the GUI. It will only show the rule if you also set Live Status = Live in the conditions.
I recommend either adding in the various options to the GUI, or disabling this in the GUI until it is fixed
…RAC-11906 to master
* commit '7fc26e8a8d6c5ed96bc414bf41a119ca33370b52':
Remove live condition for objects in lifecycle configuration.
Fixiterate-ch#11906. Fix storage class for transition to "ARCHIVE".
…RAC-11904 to master
* commit '386db225fb6ab79ca94d7cd131ed4bde197835e4':
Fixiterate-ch#11906. Copy implementation from S3 to determine if directory prefix only contains deleted objects and the marker object itself is deleted.