kitchen-cinc derives several paths automatically. Override only when your test environment deviates from the conventional layout.
These options point at directories on the workstation that the
provisioner will look at when staging the sandbox. All of them
auto-resolve to subdirectories under kitchen_root if unset.
| Option | Default subpath |
|---|---|
data_path |
data/ |
data_bags_path |
data_bags/ |
environments_path |
environments/ |
nodes_path |
nodes/ |
roles_path |
roles/ |
clients_path |
clients/ |
encrypted_data_bag_secret_key_path |
encrypted_data_bag_secret_key |
apply_path (cinc_apply only) |
apply/ |
If a path is set explicitly, the provisioner expands it relative to
kitchen_root.
These options point at executables on the test instance. The defaults
derive from cinc_omnibus_root (set by the installer at runtime). On
Windows the .bat extension is appended automatically.
- Type: String
- Default:
<cinc_omnibus_root>/bin/cinc-client - Path to the
cinc-clientbinary used during converge.
- Type: String
- Default:
<cinc_omnibus_root>/bin/cinc-solo - Path to the
cinc-solobinary used during converge.
- Type: String
- Default:
<cinc_omnibus_root>/bin/cinc-apply - Path to the
cinc-applybinary used during converge.
- Type: String
- Default:
<cinc_omnibus_root>/embedded/bin - Directory containing the embedded Ruby interpreter shipped with the Cinc package.
- The
<cinc_omnibus_root>value is populated at install time byMixlib::Install. For typical Linux installs it's/opt/cinc; for Windows it's underC:\opscode\cinc. - Override the binary paths if you install Cinc into a non-default prefix (for example, when packaging a custom omnibus build).
kitchen_rootis provided by Test Kitchen itself and points at the top of the project being tested. It is not a kitchen-cinc option.