-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Fixes non-escaped comma bug on Helm command arguments #1720
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1720 +/- ##
==========================================
+ Coverage 34.17% 34.26% +0.09%
==========================================
Files 77 77
Lines 11433 11437 +4
==========================================
+ Hits 3907 3919 +12
+ Misses 6985 6973 -12
- Partials 541 545 +4
Continue to review full report at Codecov.
|
Codecov Report
@@ Coverage Diff @@
## master #1720 +/- ##
==========================================
+ Coverage 34.17% 34.26% +0.09%
==========================================
Files 77 77
Lines 11433 11437 +4
==========================================
+ Hits 3907 3919 +12
+ Misses 6985 6973 -12
- Partials 541 545 +4
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi,
Looks good - I think we need at least one test please.
Thank you,
Alex
@alexec Done. Seems like the linter ran out of memory on the workflow check, but a local run of |
Hm, I was wondering whether this will break existing parameters that have been given with an escaped comma already, i.e. if somebody had manually worked around this issue "the Helm way" already. Also, what will happen once Helm changes this behaviour (as they have indicated in their bug reports, that they will change it one day)? |
@jannfis, fair point. I will add a check to ensure that commas don't get double-escaped. |
@jannfis Fixed the double-escaping issue. The failed test is seems unrelated. As for your other point, it seems like Helm won't break backwards compatibility without a major version bump (helm/helm#1556 (comment)). Until that decision is announced, there is no way to know how to move forward. Unless the issue here is whether this should be fixed from our end at all. If we provide a superset to helm and we provide this fix for them, then we could run into the scenario where users using ArgoCD with what they think are valid helm configs are not actually valid. By forcing users to escape their own commas, and it is made clear that the issue comes from helm, there is no such divergence. |
This commit fixes Helm parsing of parameters values containing a comma. The issue was first found as argoproj#1660, and fixed in argoproj#1720. However, commit 4e9772e, in argoproj#1865 removed the call to `cleanHelmParameters`, hence the regression.
Fixes #1660, pretty self explanatory