-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Support to force delete non-current object versions in storage bucket #8339
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
This already exists in Terraform. https://cloud.google.com/storage/docs/object-versioning I ran the Full log: https://gist.github.com/upodroid/82817606c264b484fca73f5063bd9515 Relevant snippet:
|
@rileykarson Bump 😄 |
Ah, good catch. @anubbhavm can you share debug logs from a failed attempt to destroy a bucket with versioned items? |
Signed-off-by: Modular Magician <[email protected]>
Signed-off-by: Modular Magician <[email protected]>
@anubbhavm how many objects and versions of objects are present in the bucket? |
Community Note
Description
We were testing out the
force_destroy
feature on the google cloud storage bucket resource. According to the documentation, it makes you believe that setting the variable astrue
should be enough to delete the bucket even if there are objects in the bucket. However, we have noticed that if the bucket hasversioning
enabled,force_destroy = true
is not enough and the destroy fails.We'd like to request an enhancement so that
force_destroy = true
destroys the bucket even if it has versioning enabled and some non-current object versions in it.New or Affected Resource(s)
b/275624079
The text was updated successfully, but these errors were encountered: