Updates to kitchen init
to be non-interactive (add --driver
flag), add subcommand support, and introduce kitchen driver discover
.
#71
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.
Having a non-optional interactive command is disruptive, hard to script,
and a surprising usability experience. Frankly, this author cannot
remember why he added it in the first place (late night fun with
RubyGems??).
The --driver flag defaults to
kitchen-vagrant
and can take more thanone driver if required.
This pull request also adds a new subcommand,
kitchen driver discover
whichsearches RubyGems for project names of the form 'kitchen-*'--similar to
the formerly interactive
kitchen init
command.