Tracking Pull Request Builds

[avo-sepp]

Is your feature request related to a problem? Please describe.

We have GitHub Actions producing Pull Request builds on updates to that PR. This produces a mutable tag, pr-<number> such as pr-1234.

Then I have an ArgoCD ApplicationSet which can recognize these PR builds and deploy them. As the user updates the PR, GitHub actions rebuilds upon that same mutable tag. But this time ArgoCD/Kubernetes does not know to go fetch the newest digest of the PR build.

So I tried to build something that looked like this:

argocd-image-updater.argoproj.io/image-list: pr=<repo>
argocd-image-updater.argoproj.io/pr.allow-tags: regexp:pr-\d+
argocd-image-updater.argoproj.io/pr.update-strategy: digest

Where I'd like for ArgoCD Image Updater to recognize "if I see a tag which matches the allowed tag regex, go ahead and update the digest on it". Allowing the PR builds to get updated dynamically.

This doesn't work, as the digest update strategy requires a specific tag in the image-list. So I got stuck.

Describe the solution you'd like

According to the code example above. I'd like a digest solution that can apply a digest mutation to all tags that match the allow-tags regex. This way I can reuse the same ApplicationSet for all PRs.

Describe alternatives you've considered
I couldn't think of anything better here.

[chengfang]

With current annotation-based config, it's hard to support this kind of dynamic image-list. Once we move to a image-updater CRD, that could be more flexible and hopefully be able to support your use case.