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 Pulumi WebHooks that fires on updates completing, and an API to export state files. Together you could likely implement this? See <https://www.pulumi.com/blog/getting-to-chatops-with-pulumi-webhooks/|https://www.pulumi.com/blog/getting-to-chatops-with-pulumi-webhooks/> for some content related to this. 

Not really how I want to solve it. I’ll probably wait for the long awaited ticket with proper hooks I found on github 

<https://github.com/pulumi/pulumi/issues/1691|https://github.com/pulumi/pulumi/issues/1691>

Though it’s sad to see critical functions like this take back seat to further language SDKs.

I see - you want to trigger from within the program.  You may be able to use a dynamic provider to accomplish this today - a provider which has an input property depending on the `Deployment` identity (or some particularly output which tracks changes) which forces replacement whenever the `Deployment` changes, and then makes the API call in question as part of it's `Create` handler.

Seems a little hacky. I’ll probably avoid doing this as it isn’t critical. I dislike using workarounds.