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

Dynamic provider is the way to do this right now. Pulumi doesn't currently support lifecycle hooks like you describe.

I suppose you _could_ use automation API and use the new structured logging to subscribe to pulumi engine events and depending on the event you could do some action. Haven’t explored that use case though

Yep, that sounds like a good option too. The value that you're storing or dropping would not have the same resource management lifecycle of a pulumi resource (with Create/Read/Update/Delete), but that might be okay for this use case.