-
Notifications
You must be signed in to change notification settings - Fork 40k
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
Fix kubectl create secret/configmap to allow = values #24989
Conversation
}, | ||
{ | ||
name: "err 2", | ||
input: "key=value=", | ||
err: true, | ||
key: "key", |
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.
I feel like this should be an error
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.
value= could happen in base64 output, no?
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.
we should ignore anything after the first =
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.
The root bug was the user needed the secret to store a base64 encoded value because the application consumed base64. So for example, "haha" encodes as "aGFoYQ==", the user should be able to say key=aGFoYQ== because "aGFoYQ==" is what his application is consuming. Internally, the secret will store the double encoded form, YUdGb1lRPT0=
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.
My bad, I confused myself.
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.
Yeah, i think this should be valid, then. Carry on!
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.
How about cases for "==key=value" and "key===value=="
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.
And "======"
lgtm |
97e12af
to
b9a5cf9
Compare
b9a5cf9
to
25ed62c
Compare
Rebased and reapplied lgtm since there was no code change. |
GCE e2e build/test passed for commit 25ed62c. |
🏆 |
Bug 1592653: detect int64 overflow when converting volume sizes Origin-commit: 2ca1c4f2d59ea4fb171c10923b2f24d910be79f5
Fixes #24488
@pmorie - PTAL