Knife Common Options
The following options can be run with all knife subcommands and plug-ins:
The configuration file to use. For example, when knife is run from a node that is configured to be managed by the Chef Infra Server, this option is used to allow knife to use the same credentials as Chef Infra Client looks when communicating with the Chef Infra Server.
The host to start Chef Infra Zero on. Chef Infra Zero is a lightweight, in-memory Chef Infra Server.
The port (or port range) to start chef-zero on. Port ranges like
8889-9999will try all given ports until one works.
Prevent the $EDITOR from being opened and accept data as-is.
Cause knife to 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. This option is ignored during search queries made using the
The output format:
Show help for the command.
The USER.pem file that knife uses to sign requests made by the API client to the Chef Infra Server.
View colored output.
Allows OpenSSL to enforce FIPS-validated security during a Chef Infra Client run.
Show data after a destructive operation.
The URL for the Chef Infra Server.
The user name used by knife to sign requests made by the API client to the Chef Infra Server. Authentication fails if the user name does not match the private key.
The Chef Infra Client version.
Set for more verbose outputs. Use
-VVfor much more verbose outputs. Use
-VVVfor maximum verbosity, which may provide more information than is actually helpful.
Respond to all confirmation prompts with “Yes”.
Run Chef Infra Client looks in local mode. This allows all commands that work against the Chef Infra Server to also work against the local chef-repo.