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've currently got a simple `__main__.py` that's just pulumi calls but I wand to verify some outputs and make some potential changes with native google cloud python library calls as well

It caught me off-guard that those python commands I wrote ran during the diagnostics phase as well, which of course didn't work because I was relying on the pulumi functions to have actually executed first :slightly_smiling_face:

After thinking about it more though, it makes sense that my calls would execute during the diagnostics phase as well.  So what I really want to know is how to make my bespoke python execute only after particular pulumi functions have executed "for real" (not a dry run)

Also, hi <@UB3BGTV63> !   Pinecone here :slightly_smiling_face:

You can inline pulumi code in your python code using the automation api: _(<https://github.com/pulumi/automation-api-examples/tree/main/python/inline_program>)_ 

haha, I was worried that'd be the standard response

nah, you can also run any old code during your regular `pulumi up`, you can check if it's a preview with `isDryRun` <https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/pulumi/runtime/#isDryRun>

That's exactly what I was looking for, thank you <@U01038HJ93R>!

wait you're using python, but yeah the same function (`is_dry_run`) also exists in the python sdk