Skip to content

[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

Merged
merged 3 commits into from
Nov 30, 2021
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 10 additions & 15 deletions openapi.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down Expand Up @@ -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
Copy link
Collaborator

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.

Copy link

@bcmertz bcmertz Nov 30, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You're correct @yoshizzle

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
Copy link

@bcmertz bcmertz Nov 30, 2021

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.

Copy link

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 :)

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:
Expand Down Expand Up @@ -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:
Expand Down