You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The kitchen init command provides the ability to specify a driver and provisioner. It's only fair if you can specify the transport and verifier.
I am proposing the following:
$ kitchen init --help
Usage:
kitchen kitchen:generator:init
Options:
-D, [--driver=one two three] # One or more Kitchen Driver gems to be installed or added to a Gemfile# Default: ["kitchen-vagrant"]
-P, [--provisioner=PROVISIONER] # The default Kitchen Provisioner to use# Default: chef_solo
-T, [--transport=TRANSPORT] # The default Kitchen Transport to use# Default: ssh
-V, [--verifier=VERIFIER] # The default Kitchen Verifier to use# Default: busser
[--create-gemfile], [--no-create-gemfile] # Whether or not to create a Gemfile if one does not exist. Default: false
Kitchen Version
The existing output for Test Kitchen 1.19.2.
$ kitchen version
Test Kitchen version 1.19.2
$ kitchen init --help
Usage:
kitchen kitchen:generator:init
Options:
-D, [--driver=one two three] # One or more Kitchen Driver gems to be installed or added to a Gemfile# Default: ["kitchen-vagrant"]
-P, [--provisioner=PROVISIONER] # The default Kitchen Provisioner to use# Default: chef_solo
[--create-gemfile], [--no-create-gemfile] # Whether or not to create a Gemfile if one does not exist. Default: false
The text was updated successfully, but these errors were encountered:
Description
The
kitchen init
command provides the ability to specify a driver and provisioner. It's only fair if you can specify the transport and verifier.I am proposing the following:
Kitchen Version
The existing output for Test Kitchen
1.19.2
.The text was updated successfully, but these errors were encountered: