Scroll to navigation

KNIFE-CONFIGURE(1) knife configure KNIFE-CONFIGURE(1)

NAME

knife-configure - The man page for the knife configure subcommand.

The knife configure subcommand is used to create the knife.rb and client.rb files so that they can be distributed to workstations and nodes.

Syntax

This subcommand has the following syntax when creating a knife.rb file:

$ knife configure (options)


and the following syntax when creating a client.rb file:

$ knife configure client DIRECTORY


Options

This subcommand has the following options:

The path to the private key used by the client, typically a file named admin.pem.
The name of the client, typically the name of the admin client.
The configuration file to use.
The port on which chef-zero will listen.
--[no-]color
Use to view colored output.
Use to prevent the $EDITOR from being opened and to accept data as-is.
Use to have knife use the default value instead of asking a user to provide one.
The $EDITOR that is used for all interactive commands.
The name of the environment. When this option is added to a command, the command will run only against the named environment.
The output format: summary (default), text, json, yaml, and pp.
Shows help for the command.
Use to create a API client, typically an administrator client on a freshly-installed Chef server.
The private key that knife will use to sign requests made by the API client to the Chef server.
Use to show data after a destructive operation.
The path to the chef-repo.
The URL for the Chef server.
The user name used by knife to sign requests made by the API client to the Chef server. Authentication will fail if the user name does not match the private key.
The version of the chef-client.
Set for more verbose outputs. Use -VV for maximum verbosity.
The name of the validation client.
The path to the validation key used by the client, typically a file named validation.pem.
Use to respond to all confirmation prompts with "Yes". knife will not ask for confirmation.
Use to run the chef-client in local mode. This allows all commands that work against the Chef server to also work against the local chef-repo.

Examples

$ knife configure


$ knife configure client '/directory'


AUTHOR

Chef

Chef 12.0