-
Notifications
You must be signed in to change notification settings - Fork 136
Arbitrary arguments for k8s_objects #225
Arbitrary arguments for k8s_objects #225
Conversation
Hi @samschlegel. Thanks for your PR. I'm waiting for a bazelbuild member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Hi @samschlegel , |
/ok to test |
/ok-to-test |
@samschlegel to add to what Nick mentioned. Please do not enable the controller tests. We have disabled those till we work some problems out of them. You can do the run everything on the other examples. |
So I should add them to todocontroller, but not enable the tests? |
It looks like hellogrpc also uses k8s_objects, so I could do it there instead. |
@samschlegel a grpc test would be great! |
Test added! |
Can you rebase? |
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.
Test comment
# Checks that bazel run <some target> -- <some extra arg> does pass both the | ||
# args in the attr as well as the <some extra arg> to the execution of the | ||
# template | ||
EXPECT_CONTAINS "$(bazel run examples/hellogrpc:staging.apply -- --v=1)" "apply --v=2 --v=1" |
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.
Not sure if this is your test, but we have two —v on it
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 just copied how @nlopezgi did the e2e test in hellohttp
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 dont know much about what valid args to pass, this is just testing that the arg set in the build file and the one set in the bazel run command both get passed through to the script, this doesnt really test the args actually do something meaningful
ea14d8f
to
ce06604
Compare
ugh, mac builds are timing out pulling images, will have to figure out tomorrow what's the problem |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: nlopezgi, samschlegel The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
This builds on #224 by passing through arguments to the individual runs
What would be the best way to test this?