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

Ok, so I think I want dynamic providers - they hook into the lifecycle.  I'm using C# so where can I vote for the dynamic providers in this language? :slightly_smiling_face:

I've been asking for that for a long time. The current implementation depends on it being in a weakly typed language, with the ability to serialize functions, so I think it is far off.

My question for you is - can this action be taken at the end of your destroy? Does it have to happen in the middle?

So you can do it at the end in your pipeline after executing pulumi destroy, or you can use Automation API and do it in code after executing pulumi destroy programmatically 

With automation api you can subscribe to destroy events and you can make decisions based on specific resources getting destroyed. 

Errrr I may be misremembering, you might only be able to subscribe to engine events on an UP invocation. But it's worth a look