Load user config from $HOME/.openvdc #64
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
openvdc
CLI has several common flags, that spf13/cobra says PersistentFlags. They had to be passed to the CLI everytime in order to specify the server address to connect. They should be able to save as the user local configuration file.github.com/spf13/viper
provides the feature to load configuration from multiple sources and to get merged value in loading priority.Discussions:
spf13/viper
supports multiple formats, json, yaml, toml and hcl. which is/are better to support? Or which format should be rejected..toml
and then.json
or.yaml
..hcl
can be ignored.openvdc-scheduler
should it use the same framework?TODO:
--config
flag.--server
and--master
flags to viper namespace.config.toml
if not exist.openvdc help
shows correct user home location.