-
Notifications
You must be signed in to change notification settings - Fork 262
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
fixes(#414): change plugins config keys to use - instead of camel case #428
Conversation
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.
minor nit, otherwise looks good to me.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: maximilien, rhuss 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 solves 414 by adopting new format for config keys and thereby bypassing the need for case sensitivity in Viper. Also changed `lookupPluginsInPath` key to `lookup-plugins` and also same for the persistent flag. The PATH part is implied and can be read from help.
/test pull-knative-client-integration-tests-latest-release |
/lgtm |
…ase (knative#428) This solves 414 by adopting new format for config keys and thereby bypassing the need for case sensitivity in Viper. Also changed `lookupPluginsInPath` key to `lookup-plugins` and also same for the persistent flag. The PATH part is implied and can be read from help.
Fixes #414
Proposed Changes
lookupPluginsInPath
key tolookup-plugins
and also same for the persistent flag. The PATH part is implied and can be read from help.Release Note: