-
Notifications
You must be signed in to change notification settings - Fork 75
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
'minio_s3_bucket' with versioning can't be destroyed #509
Comments
Guys, please, say something to let me know whether you care about or not. |
Hi @nixargh thanks for reporting! We do care, but we're also needing more hands to keep the project up. This provider is not sponsored by any company, and we're all using our free time to maintain it. @pjsier has opened a PR to address this issue, if you can try the solution and confirm it works, it already helps! Or if you'd like to join the maintainers team, you'd be more than welcome! |
Thank you for the answer, that is what I wanted to know and I fully understand that it is not your job. But it's important to know you are still interested in this provider as it is the best I found so far. Anyway, thanks for your job folks. |
Appreciate the understanding and help @nixargh! If you have a chance to test that PR let us know if that addresses the issue for you and we can go ahead and get that in the next release |
@pjsier, I've tested your branch and it works as expected, I mean a bucket with all its objects include versions was tottally destroyed.
|
Looks like provider doesn't remove versions of objects but just the actual version while doing force destroy. As the result terraform shows no errors but fails by timeout. After manual versions removement the bucket can be deleted.
Steps to Reproduce
I expect provider finds and deletes all versions of all objects to make force destroy.
Now versioning bucket can't be deleted via Terraform.
Provider version: 1.17.2.
Screenshot with error:
The text was updated successfully, but these errors were encountered: