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 server, this option is used to allow knife to use the same credentials as the chef-client when communicating with the Chef server.
- The port on which chef-zero listens.
- 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
knife search subcommand.
- 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 server.
- View colored output.
- Allows OpenSSL to enforce FIPS-validated security during the chef-client run.
- Show data after a destructive operation.
- 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 fails 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.
- Respond to all confirmation prompts with “Yes”.
- 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.
© Chef Software, Inc.
Licensed under the Creative Commons Attribution 3.0 Unported License.
The Chef™ Mark and Chef Logo are either registered trademarks/service marks or trademarks/servicemarks of Chef, in the United States and other countries and are used with Chef Inc's permission.
We are not affiliated with, endorsed or sponsored by Chef Inc.