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

this isn't really possible at this time I'm afraid

Thanks <@UCWG26BH7> - that was my assumption given the docs didn’t mention anything, so I’ll have to live with it.

Is it something that would be possible to do in the automation API (i.e. delete the reference to that resource in the stack as part of an automated destroy)?

I’m not really sure I want to go down that route but thought I’d check.

something to consider: it sounds like basically you want to create an S3 bucket that you "abandon" from the state - if you always want to do that, you could provision the S3 bucket using the standard AWS SDK in the automation API

it should be possible to have the state delete in the automation API i think, but you'll need to open a feature request for it

<@UCWG26BH7> indeed - that’s easy enough for an S3 bucket, but a bit harder for something like a Postgres database - have to set up connectivity for it, etc.

It would also be a bit odd with previews and so on, since that part of provisioning would execute every time, since in Go we do not have dynamic provisioners.

yeah i totally get it, i don't think there's a great answer :disappointed: your best bet would be to segment the projects and on;y run destroy on the resources you definitely want to destroy, I think

Yep, makes sense. It is what it is, not the end of the world :slightly_smiling_face: