Skip to content
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

Inclusion of force-delete=true with COS_bucket #2017

Closed
VidyasagarMSC opened this issue Nov 6, 2020 · 5 comments
Closed

Inclusion of force-delete=true with COS_bucket #2017

VidyasagarMSC opened this issue Nov 6, 2020 · 5 comments

Comments

@VidyasagarMSC
Copy link
Member

Hi there,

It would be good to have an option to force-delete a non-empty COS bucket. S3 has an option

force-delete=true

to forcible delete a non-empty COS bucket

@VidyasagarMSC VidyasagarMSC changed the title Including of force-delete=true with COS_bucket Inclusion of force-delete=true with COS_bucket Nov 6, 2020
@data-henrik
Copy link
Contributor

related to #1827

@hkantare
Copy link
Collaborator

Fixed in latest release
https://github.com/IBM-Cloud/terraform-provider-ibm/releases/tag/v1.17.0

@hkantare
Copy link
Collaborator

closing the issue

@kjoconnor
Copy link

@hkantare I'm seeing force_delete being added to my buckets that have already been created and are only getting changes to archive_rule or something easily modifiable like that. They are being marked as "in-place" modifications and not delete and recreates.

Do I need to manually set force_delete on all of my Terraform managed COS buckets now? What happens if force_delete is applied?

@hkantare
Copy link
Collaborator

hkantare commented Mar 4, 2021

force_delete is a parameter just used only during destroy.If user set this parameter it destroyed the buckets even if we have some objects attached to it. If the vlaue is false then buckets fails to destroy if it has some objects attached to it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants