-
Notifications
You must be signed in to change notification settings - Fork 69
[Update] Object Storage Cancel; Object Storage Bucket Remove #569
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
[Update] Object Storage Cancel; Object Storage Bucket Remove #569
Conversation
description: | | ||
Removes a single bucket. | ||
|
||
Bucket objects must be removed prior to removing the bucket. While buckets containing objects _may_ be |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do bucket objects need to be removed first? I thought I saw some chatter somewhere in Slack that indicated you did not need to remove first. You should confirm.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You're correct @yoshizzle
|
||
Bucket objects must be removed prior to removing the bucket. While buckets containing objects _may_ be | ||
deleted using the [s3cmd command-line tool](/docs/products/storage/object-storage/guides/s3cmd/#delete-a-bucket), such operations | ||
can fail if the bucket contains too many objects. The recommended |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"Bucket objects must be removed prior to removing the bucket" - This will no longer be true once bapi support is merged and the API force flag is deprecated.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Update: after speaking to @bbiggerr the changes here only reflect https://bits.linode.com/LinodeAPI/apinext/pull/4001 and remove reference to the force flag (prior to it being removed). With this in mind ignore the above comment :)
Nevermind, these changes only reflect asynchronously canceling ceph user, so aren't blocked by the above PR |
…s-2022-04-29 Header + Footer Updates - April 29,2022
No description provided.