argocd-image-updater
argocd-image-updater copied to clipboard
feat(chart-updater): continuous deployment of OCI Helm chart type application
Hi! There is a proposal to implement continuous deployment at the higher logical level than updating images: watch for a new helm chart versions and perform update (and included images will be updated as well). This proposal and possible solutions has been described in-depth in this issue: https://github.com/argoproj/argo-cd/issues/8475.
In this PR I've created MVP to try one solution to the problem and get your feedback if possible.
How it works
Update application targetRevision for an OCI helm chart when new chart version arrives into the container registry based on semver constraints.
Codecov Report
Merging #405 (1df2f88) into master (e46a206) will decrease coverage by
2.46%
. The diff coverage is14.70%
.
@@ Coverage Diff @@
## master #405 +/- ##
==========================================
- Coverage 65.55% 63.08% -2.47%
==========================================
Files 21 21
Lines 2032 2132 +100
==========================================
+ Hits 1332 1345 +13
- Misses 571 656 +85
- Partials 129 131 +2
Impacted Files | Coverage Δ | |
---|---|---|
pkg/argocd/update.go | 53.10% <0.00%> (-16.32%) |
:arrow_down: |
pkg/argocd/argocd.go | 65.13% <60.00%> (-1.26%) |
:arrow_down: |
pkg/argocd/git.go | 64.84% <0.00%> (ø) |
:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more
@jannfis Could you please review this ? Thank you so much
@jannfis Thanks in advance for your review.
@jannfis We really need this feature!
@distorhead Could you accept the licensing and go forward with this feature?
@distorhead Could you accept the licensing and go forward with this feature?
@mxzinke Hi! I am sorry for delayed response, accepted licensing.
@jannfis Hi! What do you think about this feature? Does it have any problems with design?
Hi @jannfis,
Could you please take a look on this PR ? Thanks.
@alexmt @jannfis anyone could take a look this pr ? thanks
Any chance this will go forward?
I really don't understand what's wrong with this PR and why repo maintainers like @jannfis don't care about this while many people are waiting for this.