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

fixes(#414): change plugins config keys to use - instead of camel case #428

Merged
merged 2 commits into from
Oct 4, 2019

Conversation

maximilien
Copy link
Contributor

@maximilien maximilien commented Oct 1, 2019

Fixes #414

Proposed Changes

  • adopts a new format for config keys and thereby bypassing the need for case sensitivity in Viper
  • changed lookupPluginsInPath key to lookup-plugins and also same for the persistent flag. The PATH part is implied and can be read from help.

Release Note:

  • 🧽 cleans up config keys to match persistent flags

@googlebot googlebot added the cla: yes Indicates the PR's author has signed the CLA. label Oct 1, 2019
@knative-prow-robot knative-prow-robot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Oct 1, 2019
Copy link
Contributor

@rhuss rhuss left a 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.

@knative-prow-robot
Copy link
Contributor

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

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.
@navidshaikh
Copy link
Collaborator

/test pull-knative-client-integration-tests-latest-release

@rhuss
Copy link
Contributor

rhuss commented Oct 4, 2019

/lgtm

@knative-prow-robot knative-prow-robot added the lgtm Indicates that a PR is ready to be merged. label Oct 4, 2019
@knative-prow-robot knative-prow-robot merged commit d543b0e into knative:master Oct 4, 2019
maximilien added a commit to maximilien/client that referenced this pull request Oct 8, 2019
…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.
@maximilien maximilien deleted the issue414 branch December 20, 2019 22:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cla: yes Indicates the PR's author has signed the CLA. lgtm Indicates that a PR is ready to be merged. 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.

~/.kn/config.yaml should accept and retain camel cased configuration
5 participants