Bricking a GCP Project for 100 years with the storage.buckets.update permission

Be careful giving users access to manage buckets in GCP. It is possible to lock a project for 100 years and if you have petabytes or whatever in there, you are stuck with it for 100 years. Not sure if support can recover it, but if they don't answer you, you are on your own and you must make a new project and move everything over.

Being able to update buckets should not give such great power with no way to recover from a misapplication of that power or in this case, no way to separate that power from other "normal" powers.