-
Notifications
You must be signed in to change notification settings - Fork 263
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for values write back in combination with Argocd-Vault-Plugin #637
base: master
Are you sure you want to change the base?
Conversation
Codecov Report
@@ Coverage Diff @@
## master #637 +/- ##
==========================================
- Coverage 65.35% 64.11% -1.25%
==========================================
Files 22 22
Lines 2084 2126 +42
==========================================
+ Hits 1362 1363 +1
- Misses 588 625 +37
- Partials 134 138 +4
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
Signed-off-by: Arnaud van Gelder <[email protected]>
Signed-off-by: Arnaud van Gelder <[email protected]>
Signed-off-by: Arnaud van Gelder <[email protected]>
2706123
to
b6393d5
Compare
Wow, this would be an huge improvement! Great work! :) Thank you! helm works now with vault plugin! :) Example:
|
great works, hope it will be merged soon. |
Can it be merged plz? |
Hello! |
Also waiting for this feature, have the same problem |
+1 |
It would be great to have a feature like this. W8 for this so long) |
Ohh, I'm really wanting for this feature, it'll make my file easier 👍 |
|
Can this be merged asap? Really need this feature |
+1 we need this feature |
argocd-image-updater doesn't support the use of plugins. This is problematic when integrations like argocd-vault-plugins are used for secrets management solutions.
This PR enables the use of ArgoCD-Vault-Plugin in combination with Helm Charts, by explicitly checking if two conditions are met:
Plugin
andIf both are true, this PR assumes a plugin is used which can process Helm charts. And as helm charts like to use
values.yaml
files (even when targetting more than 1 destination-clusters) this PR makes sure that changes are written back to a singlevalues.yaml
file. The downside of this approach is that when multiple destinations-clusters are present (so multiple Argo-Applications) there may be write-errors to git for the applications which are processed later. This is not an issue perse, as these applications will use the same (shared) values-file for deployment. If this is considered non-desired behaviour nonetheless, this can be changed into writing to application-specific values-files (like default for non-plugin write-back).