This message was deleted.
# general
s
This message was deleted.
g
Yes, it will update any YAML manifests corresponding to changed state on update.
r
hi @gorgeous-egg-16927 thanks for responding 🙂 My issue was that the pipeline runs after git commit & 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
g
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.
r
sure i can do that
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?
g
You can run
pulumi refresh
for that