Hello there, we're deploying a pulumi Stack resource in our cluster, using a flux Flux source connected to GitHub, basically following what is instructed in this documentation: https://www.pulumi.com/docs/iac/using-pulumi/continuous-delivery/pulumi-kubernetes-operator/#using-a-flux-source Our issue is with the way the resources are refreshed. Whenever the GitHub repository is updated, we can see Flux GitRepository resource getting it and building the new artifact, following the configured interval. Download said artifact with curl and decompressing the archive shows evidence the update was correctly reflected. But then, the pulumi Stack do not get refreshed before long minutes. in my last try, here was the cinematic: • git push at 4:32pm • GitRepository resource updated at 4:34pm (1 min refresh interval on resource) • Stack processed at 5:18pm (processing takes around 4/5 mins) The question is, how can we configure (here, shorten) the delay between the GitResource being refresh and the artifact produced, and the Stack being processed accordingly?

Hej @lemon-address-22717 if you dont mind me asking, I was following the same setup and trying to use a azure blob storage as backend and a azure devops repository. Are you using Pulumi Cloud or your own backend for state? If you have your own how did you go by with auth flow for that? 🙂

Hey @great-park-73778! We are using the Pulumi Cloud as state backend here. I will be not able to help you with the auth flow, sorry. 😓

ah ok, 🙂 Thanks anyhow! I have managed to got a few steps forward and will soon have something (I hope during the day) 🙂 !

Nice to hear. 🙂 Good luck with that!