Ughm, we just broke all the pipelines since the images where not updated.

haha, I wonder how we could avoid that in the future?

Can't we set the tag to latest, and deduce from the log which hash is associated to latest ? As I thought having hash was to be able to reproduce in the future, is there a gain to hardcode a specific hash in the script ?

Can't we set the tag to latest, and deduce from the log which hash is associated to latest

Even if we did that, the image would still not have been build when the change was merged. Even if the tag was :latest the pipelines would have still failed till the images where built.

The problem here was that we need to define and document a workflow for how to update this. It's not possible to both edit the images and enable features based on the changed images in the same MR.

It has to be two separate MRs to not brake things. First edit the images, wait for them to get built upstream. Then a different MR that enables the change you want and updates the image tag.

I see I really didn't understood the problem.