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

The first thing which comes to mind is Pulumi Dynamic Providers. The call which you want to do follows the resource lifecycle, where you can indicate that after the first call, there are “no changes”, so Pulumi will not “update the resource”.
<https://www.pulumi.com/docs/intro/concepts/resources/dynamic-providers/>

+1 to dynamic providers.
We also have an issue tracking adding stateful actions to programs: <https://github.com/pulumi/pulumi/issues/127>
Idea being that for some simple things (like run this code once on update, but then just use the saved state) we can have something easier to work with and lighter-weight than dynamic providers.

<https://www.pulumi.com/docs/guides/automation-api/|Pulumi's Automation API> is amazing and enables you to use Python Requests. <https://github.com/pulumi/automation-api-examples/tree/main/python|Examples here>.

It takes a bit of getting used to because the config doesn't support structured values all that well yet, but it's pretty easy to pass between scripts using YAML/JSON.