Feature Request P2
Status Update
Comments
ma...@google.com <ma...@google.com>
ma...@google.com <ma...@google.com> #2
Thanks for the report. I will route this to the appropriate internal team and update this when I hear back from them.
Description
This will create a feature request which anybody can view and comment on.
Please describe your requested enhancement. Good feature requests will solve common problems or enable new use cases.
What you would like to accomplish:
Being able to remove the lock of the retention policy for a limited period of time after it is established, so to avoid costs when it is enabled accidentally.
How this might work:
With this feature, the lock can be deleted for X days after it has been enabled in the bucket, so that the retention policy can again be modified or removed from the bucket. After X days, the lock becomes irreversible.
If applicable, reasons why alternative solutions are not sufficient:
Currently after locking a rentention policy nothing can be done.
Other information (workarounds you have tried, documentation consulted, etc):
The only possibility right now is to wait for the retention policy to be satisfied by all the objects in the bucket, and then delete the bucket, so the locked retention policy is deleted, or to remove the whole project.