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

I haven't, but a generic pattern that works in this situation is to have two projects; one for the droplet + contents, and one for everything outside it. StackReferences to share data. That way, you can safely destroy / up the droplet stack on every deploy.

Hmm it seems so obvious now. This might solve the problem. It’s def a workaround but better than the mess I have now I think…thanks!