Force a re-run even when there is no change in the git repository

[dirien]

Hello!

• Vote on this issue by adding a 👍 reaction
• If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

Feedback from on of our customers:

It would be great if we can have a documented and reliable way to force a pulumi run even when a git change has not be made.

Customer is implementing currently continueResyncOnCommitMatch but would still love to see this feature in the future.

[squaremo]

I'm not clear on what the motivation is -- can you elaborate on the circumstances in which you want to run the stack, and why continueResyncOnCommitMatch: true is not quite right?

For comparison: https://github.com/pulumi/pulumi-kubernetes-operator/issues/397 regards running stacks when the spec changes but not on a schedule; and, the PR https://github.com/pulumi/pulumi-kubernetes-operator/pull/320 adds (incidentally) a way to trigger a stack run at any time by annotating the Stack object.

[EronWright]

My understanding of this enhancement request is to provide a manual re-sync trigger, i.e. pulumi up on demand. Good news is that the pulumi.com/reconciliation-request annotation is understood to have the semantic that it forces a re-sync, and was re-implemented in https://github.com/pulumi/pulumi-kubernetes-operator/pull/745.

Here's an example that demonstrates the functionality (via the higher-level prerequisites feature).