updatecli VS keel

Updatecli is a useful tool for fine-tuning update strategies in DevOps. As you've probably experienced, manual updates often result in outdated specs because figuring out what can be updated is tricky.

A second innovation is the use of updatecli to observe the available application helm releases and update the environment helm charts automatically to promote application versions:

Maybe you could have a look to Updatecli https://github.com/updatecli/updatecli

I built https://github.com/updatecli/updatecli for those situations where it's not possible to guess the next tag version. It's a declarative dependency management tool, You define in a manifest how your Yaml should be update, then run updatecli from your CI to automatically open a PullRequest on your repository when a new container tag is available.

Like in this package https://github.com/updatecli/updatecli/tree/main/pkg/plugins...

And the matching between a package and a resource kind is done here

I just want to throw in keel as another alternative.

There are multiple tools available for that. Another one could be https://keel.sh

Flux for Kubernetes and we have installed Keel to let devs restart deployments on Development cluster. We don't use Webhooks but just have them do Powershell request to endpoint either in their pipeline or manually depending on dev teams desire.

Have you seen keel? https://github.com/keel-hq/keel I'm using it on very small projects with very simple delivery logic, so I'm not sure if it's gonna work out in your case, you can give it a try though.

There is also a 3rd party tool like Keel but it doesn't support Amazon ECR (Webhook problem with ECR).

This got a little off track... I don't have a problem. You have a problem! but TLDR; keel?

I’ve used keel to help me with this issue: https://keel.sh.

Keel might be of interest.

I've used Keel and more recently ArgoCD Image Updater (Using ArgoCD to manage deployments).