Is it possible to only run a step if it's changing the image(s) versions?

[danielloader]

Extending one of my questions around running a http step if any of the stages prior fail - thus notifying on failure.

Is it possible to run a step if it's an image change only?

Would be getting a lot of noisy notifications when debugging yaml in the manifests and punching dozens of commits up when the deployed image hasn't changed at all.

[krancour]

There's an open issue for conditional steps, but I'm not clear on where all the noise is coming from. Doing something like kustomize-update-image when the image hasn't changed, should amount to a no-op. It shouldn't result in any diffs. If none of the steps resulted in any diffs, then even the push step amounts to a no-op.

I trust that you're getting some noise. I'm just not clear on where it's coming from.

[danielloader]

Yeah you're correct on the kustomize-update-image - and I really should retool around it... currently using argocd-update and due to that tracking the manifests, and those manifests changing, that triggers a new freight which ultimately triggers the http slack webhook.

[krancour]

Ahhh. That makes sense. A word of caution. If you just update Apps with new image info, it's not "real gitops" as you don't have anything in git that says definitively what image that App is referencing at any point in time. It sure is convenient though. I see it mainly as existing to facilitate experimentation with less overhead.

[danielloader]

For sure, and I will be experimenting to find out how best to handle a more rendered static git driven flow shortly.

Just need to work out how to do so sanely with a monorepo of manifests.

[krancour]

Just in case you haven't seen this other thread, it may help: #3203