-
Notifications
You must be signed in to change notification settings - Fork 770
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
support parse key-only environment variable #317
Conversation
👍 |
yeah, let's blocked everything until we get in the habit of making sure we have unit tests... |
ok so @kadel I added the unit test. Please take a look. |
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.
LGTM with the exception of the merge-conflict.
Tks @cdrage Rebased! |
LGTM 👍 |
@cdrage please approve again then I can merge it. |
@ngtuna I can approve, but since I still don't have access to @kubernetes-incubator it wont appear as 👍 / green. |
{ev2, rs2}, | ||
{ev3, rs3}, | ||
{ev4, rs4}, | ||
} |
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.
why not do it in literal form in here itself than declaring multiple variables? I don't say it's bad/wrong or not, just curious?
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.
Well It's just for making test cases looks clearly.
@cdrage I see :-( |
@ngtuna Also three more conditions that are not tested: env: "foo:bar=foobar" name: "foo" val: "bar=foobar"
env: "foo=foo:bar" name: "foo" val: "foo:bar"
env: "foo:" name: "foo" val: "" otherwise LGTM |
@surajssd Added and rebased. Please take a look and approve if it's okay for you. |
fix #303