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

to ensure it’s rendered from fresh when required

does doing a `pulumi refresh` before `pulumi up` not suffice? Are you working with resources that have state defined outside Pulumi that you would like to "reset"?

Currently, I’m purely using Pulumi to render Kubernetes manifests out to disk before manually applying them

But even if I didn’t render them to disk, I’m thinking of a CI scenario without any persistent state