summaryrefslogtreecommitdiff
path: root/lib
Commit message (Collapse)AuthorAgeFilesLines
* Bump version to 2.1.10 by Chef Expeditorv2.1.10Chef Expeditor2021-06-251-1/+1
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* Bump version to 2.1.9 by Chef Expeditorv2.1.9Chef Expeditor2020-09-161-1/+1
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* Bump version to 2.1.8 by Chef Expeditorv2.1.8Chef Expeditor2020-08-211-1/+1
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* Merge pull request #78 from chef/requiresTim Smith2020-08-211-1/+1
|\ | | | | Signed-off-by: Tim Smith <tsmith@chef.io>
| * Optimize our requiresTim Smith2020-08-211-1/+1
| | | | | | | | | | | | Avoid requiring things that are already defined. Rubygems is very slow at traversing the filesystem. Signed-off-by: Tim Smith <tsmith@chef.io>
* | Bump version to 2.1.7 by Chef Expeditorv2.1.7Chef Expeditor2020-08-211-1/+1
| | | | | | | | Obvious fix; these changes are the result of automation not creative thinking.
* | Fix minor typosspellingTim Smith2020-07-282-3/+3
|/ | | | Signed-off-by: Tim Smith <tsmith@chef.io>
* Bump version to 2.1.6 by Chef Expeditorv2.1.6Chef Expeditor2019-12-221-1/+1
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* Substitute require for require_relativerelativeTim Smith2019-12-201-1/+1
| | | | | | require_relative is significantly faster and should be used when available. Signed-off-by: Tim Smith <tsmith@chef.io>
* Bump version to 2.1.5 by Chef Expeditorv2.1.5Chef Expeditor2019-12-191-1/+1
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* Bump version to 2.1.4 by Chef Expeditorv2.1.4Chef Expeditor2019-08-281-1/+1
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* Bump version to 2.1.3 by Chef Expeditor2.1.3Chef Expeditor2019-07-121-1/+1
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* Fix chefstyleVivek Singh2019-07-122-25/+29
| | | | Signed-off-by: Vivek Singh <vivek.singh@msystechnologies.com>
* Bump version to 2.1.2 by Chef Expeditor2.1.2Chef Expeditor2019-06-251-1/+1
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* Bump version to 2.1.1 by Chef Expeditor2.1.1Chef Expeditor2019-06-101-1/+1
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* Don't explode when there are unknown keys in 'config'deprecation-fix-unknown-keysMarc A. Paradise2019-06-071-1/+6
| | | | | | | 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>
* Bump version to 2.1.0 by Chef Expeditor2.1.0Chef Expeditor2019-06-071-1/+1
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* Merge pull request #65 from chef/MIXLIB-CLI-63/deprecated-option-supportTim Smith2019-06-062-30/+167
|\ | | | | [MIXLIB-CLI-63] Add deprecated_option support
| * Code review updates for deprecated_optionMIXLIB-CLI-63/deprecated-option-supportMarc A. Paradise2019-06-062-11/+12
| | | | | | | | Signed-off-by: Marc A. Paradise <marc.paradise@gmail.com>
| * [MIXLIB-CLI-63] Add deprecated_option supportMarc A. Paradise2019-06-062-30/+166
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
* | Bump version to 2.0.9 by Chef Expeditor2.0.9Chef Expeditor2019-06-051-1/+1
|/ | | | Obvious fix; these changes are the result of automation not creative thinking.
* Bump version to 2.0.8 by Chef Expeditor2.0.8Chef Expeditor2019-06-011-1/+1
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* Bump version to 2.0.7 by Chef Expeditor2.0.7Chef Expeditor2019-06-011-1/+1
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* Bump version to 2.0.6 by Chef Expeditorv2.0.6Chef Expeditor2019-05-141-1/+1
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* Add more specs and use or not andTim Smith2019-05-131-3/+3
| | | | | | This seems to make more sense Signed-off-by: Tim Smith <tsmith@chef.io>
* Print out human readable lists of allowed CLI optionsTim Smith2019-05-131-3/+13
| | | | | | 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>
* Bump version to 2.0.5 by Chef Expeditorv2.0.5Chef Expeditor2019-05-141-1/+1
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* Improve the --help text output of 'in:'btm/included_textBryan McLellan2019-05-131-1/+1
| | | | | | | 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>
* Bump version to 2.0.4 by Chef Expeditorv2.0.4Chef Expeditor2019-04-231-1/+1
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* Bump version to 2.0.3 by Chef Expeditorv2.0.3Chef Expeditor2019-03-201-1/+1
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* Bump version to 2.0.2 by Chef Expeditorv2.0.2Chef Expeditor2019-01-041-1/+1
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* Bump version to 2.0.1 by Chef Expeditorv2.0.1Chef Expeditor2019-01-041-1/+1
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* actually do the major version bumpLamont Granquist2019-01-041-1/+1
| | | | | | expeditor at the last one, gotta bump VERSION Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* Bump version to 1.7.7 by Chef Expeditorv1.7.7Chef Expeditor2019-01-041-1/+1
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* update travis, drop ruby < 2.5, major version bumpLamont Granquist2019-01-041-1/+1
| | | | | | solely major version bump for the ruby support floor Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* Bump version to 1.7.6 by Chef Expeditorv1.7.6Chef Expeditor2018-09-181-1/+1
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* Bump version to 1.7.5 by Chef Expeditorv1.7.5Chef Expeditor2018-08-021-1/+1
|
* Bump version to 1.7.4 by Chef Expeditorv1.7.4Chef Expeditor2018-07-311-1/+1
|
* Bump version to 1.7.3 by Chef Expeditorv1.7.3Chef Expeditor2018-07-301-1/+1
|
* Chefstyle fixesTim Smith2018-07-302-6/+6
| | | | Signed-off-by: Tim Smith <tsmith@chef.io>
* Bump version to 1.7.2 by Chef Expeditorv1.7.2Chef Expeditor2018-07-241-1/+1
|
* Bump version to 1.7.1 by Chef Expeditorv1.7.1Chef Expeditor2018-06-261-1/+1
|
* bugfix: if param :required is set to false and param :in is set the option ↵Yuri Zubov2018-03-231-1/+1
| | | | | | is required Signed-off-by: Yuri Zubov <y.zubov@sumatosoft.com>
* Avoid modification on possibly frozen stringGrégoire Seux2017-09-171-1/+2
| | | | | | | | | Most users are defining option description with string literal. Starting from ruby 2.3, rubocop starts advocating to set `# frozen_string_literal: true` magic comment. Before this patch, this would raise an error related to modification of frozen string. Change-Id: Ia2561296a5855e639a4972368ab00ccbccd7cb12 Signed-off-by: Grégoire Seux <g.seux@criteo.com>
* fix chefstyle offensesLamont Granquist2017-06-201-1/+1
| | | | Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* Opscode -> ChefTim Smith2016-08-231-2/+2
| | | | Signed-off-by: Tim Smith <tsmith@chef.io>
* Release 1.7.0v1.7.0Thom May2016-07-061-1/+1
| | | | Signed-off-by: Thom May <thom@may.lt>
* Make chefstyle happy.Noah Kantrowitz2016-06-161-11/+11
|
* Support two-argument procs for reducer-style arguments. This allows CLI ↵Noah Kantrowitz2016-06-161-1/+12
| | | | options which can be repeated.
* Release 1.6.0v1.6.0Thom May2016-05-051-1/+1
| | | | Signed-off-by: Thom May <thom@may.lt>
View Lorry Controller Status