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

Yes, it will update any YAML manifests corresponding to changed state on update.

hi <@UE1LN7A22> thanks for responding :slightly_smiling_face: My issue was that the pipeline runs after git commit &amp; push, and the output files are never committed to git for comparison the next time round

I found a potential workaround though which is changing the output dir each build, which forces pulumi to re-write them all

Ah, understood. Would you mind opening an issue in the pulumi-kubernetes repo about this? I think the provider should check that all of the expected files exist rather than just the changed ones, so this is probably a bug.

i have a follow up question aswell, is it possible to setup the provider so that it always updates the cluster with ALL of resources, regardless of whether or not it detects a change. I ask because if you manually change something on the cluster, it won’t go back to desired state on next pulumi up. Does that make sense?