| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Signed-off-by: jayashri garud <jgarud@msystechnologies.com>
|
|
|
|
|
| |
Signed-off-by: Tim Smith <tsmith@chef.io>
Co-authored-by: pete higgins <pete@peterhiggins.org>
|
|
|
|
|
| |
Signed-off-by: Tim Smith <tsmith@chef.io>
Co-authored-by: pete higgins <pete@peterhiggins.org>
|
|
|
|
|
|
| |
This makes these bits easier to read
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Signed-off-by: Vivek Singh <vivek.singh@msystechnologies.com>
|
|
|
|
|
|
|
| |
Update handle_deprecated_options to be graceful when
'config' has been modified externally to contain unknown keys.
Signed-off-by: Marc A. Paradise <marc.paradise@gmail.com>
|
|
|
|
| |
Signed-off-by: Marc A. Paradise <marc.paradise@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This commit adds deprecated option support by exposing a
new ClassMethod, `deprecated_option`. It will generate a
corresponding deprecated option, and if that option is used it will
handle mapping of the old option to the new and issue a warning.
`deprecated_option` accepts a subset of the parameters that `option` accepts.
Most importantly, a deprecated option can't have a default value.
There's a practical reason for this and a philosophical one.
Practically, it makes it easy to track the situation where someone has
set `use_separate_defaults` to `false`. In that case, we currently
can't tell whether the user provided the flag, or it was set as a default.
This could have been addressed, but:
Philosphically it makes more sense to not have a default value on a
deprecated item. If it's deprecated, you want people to stop using it.
If it has a default, it's effectively forced in-use at all times.
See function docs for further accepted parameters.
To allow deprecated options without warnings, use parse_options as
`parse_options(ARGV, show_deprecations: false)`. By default, warnings
will be shown.
This also moves some formatting code into its own class -
it was causing methods to get mixed in that client classes didn't
need; and I reached the point where I needed to access the formatting
functions across methods in both Mixlib::CLI and
Mixlib::CLI::ClassMethods. It made more sense to move them outside of
the mixed-in bits, since it wasn't a concern of the caller that would be
inheriting those methods.
Signed-off-by: Marc A. Paradise <marc.paradise@gmail.com>
|
|
|
|
|
|
| |
This seems to make more sense
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
| |
Give a nice friendly sentence and not an array. This uses the code we nuked from chef/chef that did the same.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
|
| |
The automatic addition of the 'in' options to the --help output could be
more clear about what the list is.
Signed-off-by: Bryan McLellan <btm@loftninjas.org>
|
|
|
|
| |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
|
|
|
|
|
|
| |
since classes are global state, having a single TestCLI class that
threads through all the examples creates state pollution that can
cause ordering problems.
solve this by rewiring TestCLI to a new class every single time.
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
| |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
|
|
| |
is required
Signed-off-by: Yuri Zubov <y.zubov@sumatosoft.com>
|
|
|
|
| |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
| |
This could be further fixed, but this gets us on 3.X without deprecation warnings
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
|
|
|
|
| |
options which can be repeated.
|
|
|
|
| |
Signed-off-by: Thom May <thom@may.lt>
|
|\
| |
| | |
[MIXLIB-14] Option inheritance
|
| | |
|
| | |
|
| |
| |
| |
| | |
isolation.
|
| | |
|
| | |
|
| | |
|
|\ \
| | |
| | |
| | |
| | | |
Conflicts:
lib/mixlib/cli.rb
|
| | | |
|
| |/ |
|
| | |
|
|/
|
|
| |
the given list
|
|
|
|
|
|
|
| |
This will make it easier for knife to apply config settings in the
proper order (default < config file < command line). It's not possible
to do without this patch because knife must parse command line options
to determine which config file to use.
|
| |
|
| |
|
|
|
|
|
| |
Using --[no-]xxx on a boolean parameter lets the
user specify the value as false, like in
OptionParser.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|