Skip to content
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

Merged
merged 1 commit into from
May 6, 2016

Conversation

derekwaynecarr
Copy link
Member

Fixes #24488

@pmorie - PTAL

@derekwaynecarr derekwaynecarr added the release-note-none Denotes a PR that doesn't merit a release note. label Apr 29, 2016
},
{
name: "err 2",
input: "key=value=",
err: true,
key: "key",
Copy link
Member

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

Copy link
Member Author

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?

Copy link
Member Author

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 =

Copy link
Member Author

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=

Copy link
Member

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.

Copy link
Member

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!

Copy link
Member

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=="

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

And "======"

@k8s-github-robot k8s-github-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Apr 29, 2016
@deads2k
Copy link
Contributor

deads2k commented Apr 29, 2016

lgtm

@deads2k deads2k added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Apr 29, 2016
@derekwaynecarr
Copy link
Member Author

@k8s-bot test this issue #24991

@derekwaynecarr
Copy link
Member Author

@k8s-bot test this issue #24991

@k8s-github-robot k8s-github-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label May 2, 2016
@derekwaynecarr derekwaynecarr added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label May 3, 2016
@k8s-github-robot k8s-github-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label May 4, 2016
@derekwaynecarr derekwaynecarr added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label May 4, 2016
@derekwaynecarr
Copy link
Member Author

Rebased and reapplied lgtm since there was no code change.

@derekwaynecarr derekwaynecarr added this to the v1.3 milestone May 5, 2016
@k8s-bot
Copy link

k8s-bot commented May 6, 2016

GCE e2e build/test passed for commit 25ed62c.

@roberthbailey roberthbailey merged commit 0db3ca4 into kubernetes:master May 6, 2016
@pmorie
Copy link
Member

pmorie commented May 6, 2016

🏆

@derekwaynecarr derekwaynecarr added release-note Denotes a PR that will be considered when it comes time to generate release notes. and removed release-note-none Denotes a PR that doesn't merit a release note. labels Jun 9, 2016
openshift-publish-robot pushed a commit to openshift/kubernetes that referenced this pull request May 18, 2020
Bug 1592653: detect int64 overflow when converting volume sizes

Origin-commit: 2ca1c4f2d59ea4fb171c10923b2f24d910be79f5
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lgtm "Looks good to me", indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants