This message was deleted.

Which CRD are you talking about — do you mean a Stack object, or a Program object?

a Stack object 👍

I see, so you want stack runs to be triggered by a change to the Stack object, but not run on a schedule. Setting .continueSyncOnCommitMatch means it’ll run on a schedule; not setting it means when the stack object changes, it’ll usually not run the stack because the commit didn’t change.

Yes, basically I would expect the operator to monitor both changes in the git repository (programs) and in the Stack definition, I guess it would be a simple and logical thing to do.. for me it sounds like somebody forgot to implement it 😄

It is more that the sensibility of the Pulumi command-line tool was carried over into the operator. The base assumption is that you only want to update the stack when you changed your code (and therefore there’s something to change), and not to spend resources running it otherwise. So, the operator will notice if a Stack has changed, but abandon the update if it’s already been run at that commit.

Ah, nice! Thanks for the information @eager-football-6317, I'll watch this one 👍