-
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -504,8 +504,7 @@ paths: | |
survey_link: | ||
type: string | ||
description: A link to Linode's exit survey. | ||
example: {'survey_link': | ||
'https://alinktothesurvey.com'} | ||
example: {'survey_link': https://alinktothesurvey.com'} | ||
'409': | ||
description: Could not charge the credit card on file | ||
content: | ||
|
@@ -12561,14 +12560,15 @@ paths: | |
servers: | ||
- url: https://api.linode.com/v4 | ||
summary: Object Storage Bucket Remove | ||
description: > | ||
Removes a single bucket. While buckets containing objects _may_ be | ||
deleted by including the `force` option in the request, such operations | ||
will fail if the bucket contains too many objects. The recommended | ||
description: | | ||
Removes a single bucket. | ||
|
||
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 commentThe reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment. Choose a reason for hiding this commentThe 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 :) |
||
way to empty large buckets is to use the [S3 API to configure lifecycle policies](https://docs.ceph.com/en/latest/radosgw/bucketpolicy/#) that | ||
remove all objects, then delete the bucket. | ||
|
||
|
||
This endpoint is available for convenience. It is recommended that instead you | ||
use the more [fully-featured S3 API](https://docs.ceph.com/en/latest/radosgw/s3/bucketops/#delete-bucket) directly. | ||
tags: | ||
|
@@ -13443,14 +13443,9 @@ paths: | |
- url: https://api.linode.com/v4 | ||
summary: Object Storage Cancel | ||
description: | | ||
Cancel Object Storage on an Account. All buckets on the Account must be empty | ||
before Object Storage can be cancelled: | ||
|
||
- To delete a smaller number of objects, review the instructions in our | ||
[How to Use Object Storage](/docs/platform/object-storage/how-to-use-object-storage/) | ||
guide. | ||
- To delete large amounts of objects, consult our guide on | ||
[Lifecycle Policies](/docs/platform/object-storage/lifecycle-policies/). | ||
Cancel Object Storage on an Account. | ||
|
||
**Warning**: Removes all buckets and their contents from your Account. This data is irretrievable once removed. | ||
security: | ||
- personalAccessToken: [] | ||
- oauth: | ||
|
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.
Uh oh!
There was an error while loading. Please reload this page.
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