-
Notifications
You must be signed in to change notification settings - Fork 3.4k
fix: handle escape chars in withParam/withItems. Fixes #13718 #14864
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
Conversation
51a5ad0 to
e50be2e
Compare
Signed-off-by: Tzu-Ting <[email protected]>
7788c6e to
1641d2b
Compare
1641d2b to
abfa425
Compare
Signed-off-by: Tzu-Ting <[email protected]>
abfa425 to
fb957c6
Compare
|
Note for the failed tests On Dec 2025, I rebased the branch to reflect the changes from 2672ba3 and found the test "CI / E2E Tests (test-python-sdk)" failed. This PR is focused on the logic in |
|
/retest |
1 similar comment
|
/retest |
|
Thanks for the thorough tests! You're correct that the failures with |
|
/retest |
MasonM
left a comment
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.
Good job @tzing! I appreciate your persistence
Fixes #13718
Motivation
On using withParam/withItems on DAG/Steps, Argo Workflow mistakenly replace the
\nchars as\\nand it may break some tasks.Modifications
The operator used a JSON serialized string for building items. This casues some escape string got escaped again.
This PR use the the
GetStrValmethod to extract its original value.Verification
Covered in the test cases added in fb957c6
Documentation