Skip to content
This repository has been archived by the owner on Jun 28, 2023. It is now read-only.

Handle empty CLI default config values #2347

Merged

Conversation

stmcginnis
Copy link
Contributor

Initializing the local cluster configuration was checking for the
presence of config settings, but not whether they actually contained a
value. This is a problem with the real CLI processing since the default
values set on all options ends up being "", resulting in default values
being used unless passed in as a command line argument.

Initializing the local cluster configuration was checking for the
presence of config settings, but not whether they actually contained a
value. This is a problem with the real CLI processing since the default
values set on all options ends up being "", resulting in default values
being used unless passed in as a command line argument.

Signed-off-by: Sean McGinnis <[email protected]>
@stmcginnis stmcginnis requested a review from a team as a code owner October 25, 2021 19:45
@joshrosso joshrosso merged commit a58833d into vmware-tanzu:standalone-overhaul Oct 25, 2021
@stmcginnis stmcginnis deleted the sa-overhaul-configinit branch October 25, 2021 20:41
joshrosso pushed a commit that referenced this pull request Jan 18, 2022
Initializing the local cluster configuration was checking for the
presence of config settings, but not whether they actually contained a
value. This is a problem with the real CLI processing since the default
values set on all options ends up being "", resulting in default values
being used unless passed in as a command line argument.

Signed-off-by: Sean McGinnis <[email protected]>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants