No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

There is a forceDestroy param that you can set as part of the bucket - you will need to apply that parameter first and then you can run a destroy

nah, that's not it, it will bail out saying the bucket is not empty if that's the case.

if i want to destroy something with content, i export the stack, edit `forceDestroy` to be `true`, then re-import, and then run the destroy

You can't delete a bucket with versioning turned on:
<https://aws.amazon.com/premiumsupport/knowledge-center/delete-bucket-s3-console-cli/>
you can only suspend the bucket.

<@UM6PHB1RS> that's what I was saying - you need to apply that parameter first so that it is part of the state - THEN you can run the deploy

<@UHTP242EB> yup, as i said, that's exactly what i did, that's not the issue.
<@U019AM8NP1A> ah i see, i guess the implication is that pulumi doesn't empty the bucket before attempting to delete it?

if i completely empty the bucket using the console, i can then delete the bucket through pulumi, so i imagine that's it.

<@U019AM8NP1A> from the page you linked, i get the sense the requests to aws should fail (rather than hang forever) -- do you know if that is indeed the case?

<@UM6PHB1RS> I don't know if that is the expected behavior.

<@UM6PHB1RS> this is a bug then - forceDestroy *SHOULD* delete all objects!

<@UHTP242EB> i've submitted <https://github.com/pulumi/pulumi-aws/issues/1132>