|
OverviewKnife is a command-line tool that comes with Chef.It is used by administrators to interact with the Chef Server API, the local Chef repository and and can be used to create, edit, view, list, and delete API clients.
|
|
|
The following client arguments are available: bulk deleteDelete clients where the client name matches the regular expression [regex] on the Chef Server. The regular expression should be given as a quoted string, and not surrounded by forward slashes. createCreate a new client. This generates an RSA keypair. The private key will be displayed on STDOUT or written to the named file. The public half will be stored on the Server. For chef-client systems, the private key should be copied to the system as /etc/chef/client.pem. If you do not copy the key and try running chef-client for the first time without it, you will get a 403 error because you won't have sufficient permissions to re-create the key. Admin clients should be created for users that will use knife to access the API as an administrator. The private key will generally be copied to ~/.chef/client_name.pem and referenced in the knife.rb configuration file. Hosted Chef users should note that marking clients as "Admin clients" will have no effect when using Hosted Chef. Usage: Additional Options:
deleteDeletes a registered client. Usage: editEdit a registered client. Usage: The clients record will be open with EDITOR and can be edited by the user. listList all registered clients Usage: Additional Options:
Example Output: reregisterRegenerate the RSA keypair for a client. The public half will be stored on the server and the private key displayed on STDOUT or written to the named file. This operation will invalidate the previous keypair used by the client, preventing it from authenticating with the Chef Server. Use care when reregistering the validator client. Usage: Additional Options:
showShow a client. Output format is determined by the --format option. Usage: Additional Options:
Example Output
|
|
|


