-
Notifications
You must be signed in to change notification settings - Fork 29
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
I-134 Add --in-cluster key for provisioner #135
base: master
Are you sure you want to change the base?
Conversation
Codecov Report
@@ Coverage Diff @@
## master #135 +/- ##
==========================================
- Coverage 78.49% 78.19% -0.30%
==========================================
Files 22 22
Lines 1432 1440 +8
==========================================
+ Hits 1124 1126 +2
- Misses 308 314 +6
Continue to review full report at Codecov.
|
@@ -161,6 +169,8 @@ def _handler_provision(command, resources, priority_evaluator, use_kubeconfig, s | |||
help='Check existence of all env variables in config.yaml and stop if var is not set') | |||
parser_provisioning.add_argument('--use-kubeconfig', action='store_true', required=False, | |||
help='Try to use kube config') | |||
parser_provisioning.add_argument('--in-cluster', action='store_true', required=False, |
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.
It think that if kube-config configuration and in-cluster configuration options are mutually exclusive by idea and by design, they should be mutually exclusive at arguments parser's level as well.
Now we can specify both and the kube-config will be implicitly used.
As a little effort, I'd try to add them into add_mutually_exclusive_group(), if it works correctly with subparsers.
Fixes #135