knife-configure(1) [debian man page]

KNIFE-CONFIGURE(1)						    Chef Manual 						KNIFE-CONFIGURE(1)

NAME

       knife-configure - Generate configuration files for knife or Chef Client

SYNOPSIS

       knife configure [client] (options)

DESCRIPTION

       Generates a knife.rb configuration file interactively. When given the --initial option, also creates a new administrative user.

CONFIGURE SUBCOMMANDS

       knife configure (options)

       -i, --initial
	      Create an initial API Client

       -r, --repository REPO
	      The path to your chef-repo

       Create  a configuration file for knife. This will prompt for values to enter into the file. Default values are listed in square brackets if
       no other entry is typed. See knife(1) for a description of configuration options.

       knife configure client directory

       Read the knife.rb config file and generate a config file suitable for use in /etc/chef/client.rb and copy the validation  certificate  into
       the specified directory.

EXAMPLES

       o   On  a  freshly  installed  Chef Server, use knife configure -i to create an administrator and knife configuration file. Leave the field
	   blank to accept the default value. On most systems, the default values are acceptable.

	   user@host$ knife configure -i
	   Please enter the chef server URL: [http://localhost:4000]
	   Please enter a clientname for the new client: [username]
	   Please enter the existing admin clientname: [chef-webui]
	   Please enter the location of the existing admin client's private key: [/etc/chef/webui.pem]
	   Please enter the validation clientname: [chef-validator]
	   Please enter the location of the validation key: [/etc/chef/validation.pem]
	   Please enter the path to a chef repository (or leave blank):
	   Creating initial API user...
	   Created (or updated) client[username]
	   Configuration file written to /home/username/.chef/knife.rb

	   This creates a new administrator client named username, writes a configuration file to /home/username/.chef/knife.rb, and  the  private
	   key to /home/username/.chef/username.pem. The configuration file and private key may be copied to another system to facilitate adminis-
	   tration of the Chef Server from a remote system. Depending on the value given for the Chef Server URL, you may need to modify that set-
	   ting after copying to a remote host.

SEE ALSO

       knife(1) knife-client(1)

AUTHOR

       Chef was written by Adam Jacob adam@opscode.com with many contributions from the community.

DOCUMENTATION

       This  manual  page was written by Joshua Timberman joshua@opscode.com. Permission is granted to copy, distribute and / or modify this docu-
       ment under the terms of the Apache 2.0 License.

CHEF

       Knife is distributed with Chef. http://wiki.opscode.com/display/chef/Home

Chef 10.12.0							     June 2012							KNIFE-CONFIGURE(1)

KNIFE-DATA-BAG(1)						    Chef Manual 						 KNIFE-DATA-BAG(1)

NAME

       knife-data-bag - Store arbitrary data on a Chef Server

SYNOPSIS

       knife data bag sub-command (options)

DESCRIPTION

       Data  bags  are stores of arbitrary JSON data. Each data bag is a collection that may contain many items. Data Bag Items are indexed by the
       Chef Server and can be searched via knife-search(1).

       Data bags are available to all nodes configured by chef-client(8), and are therefore a convenient mechanism to  store  global  information,
       such as lists of administrative accounts that should be configured on all hosts.

DATA BAG SUB-COMMANDS
CREATE

       knife data bag create bag name [item id] (options)

       -s, --secret SECRET
	      A secret key used to encrypt the data bag item. See encryption support below.

       --secret-file SECRET_FILE
	      The path to a file containing the secret key to be used to encrypt the data bag item.

       If  item  id  is given, creates a new, empty data bag item and opens it for editing in your editor. The data bag will be created if it does
       not exist.

       If item id is not given, the data bag will be created.

DELETE

       knife data bag delete bag name [item id] (options)

       Delete a data bag, or an item from a data bag.

EDIT

       knife data bag edit bag name item id (options)

       -s, --secret SECRET
	      A secret key used to encrypt the data bag item. See encryption support below.

       --secret-file SECRET_FILE
	      The path to a file containing the secret key to be used to encrypt the data bag item.

       Edit an item in a data bag.

FROM FILE

       knife data bag from file bag name file (options)

       knife data bag from file bag name file1 file2 file3 (options)

       knife data bag from file bag name folder (options)

       -s, --secret SECRET
	      A secret key used to encrypt the data bag item. See encryption support below.

       --secret-file SECRET_FILE
	      The path to a file containing the secret key to be used to encrypt the data bag item.

       Load a data bag item from a JSON file. If file is a relative or absolute path to the file, that file will  be  used.  Otherwise,  the  file
       parameter  is  treated  as  the	base  name  of	a  data  bag  file  in	a  Chef  repository,  and  knife  will	search	for  the  file	in
       ./data_bags/bag_name/file. For example knife data bag from file users dan.json would attempt to load the file ./data_bags/users/dan.json.

LIST

       knife data bag list (options)

       -w, --with-uri
	      Show corresponding URIs

       Lists the data bags that exist on the Chef Server.

SHOW

       knife data bag show BAG [ITEM] (options)

       -s, --secret SECRET
	      A secret key used to encrypt the data bag item. See encryption support below.

       --secret-file SECRET_FILE
	      The path to a file containing the secret key to be used to encrypt the data bag item.

       Show a specific data bag or an item in a data bag. The output will be formatted according to the --format option.

ENCRYPTION SUPPORT

       Data Bag Items may be encrypted to keep their contents secret. This may be desireable when storing sensitive information such  as  database
       passwords, API keys, etc.

       Data Bag Item encryption uses the AES-256 CBC symmetric key algorithm.

       CAVEATS:  Keys  are not encrypted; only values are encrypted. The "id" of a Data Bag Item is not encrypted, since it is used by Chef Server
       to store the item in its database. For example, given the following data bag item:

	   {"id": "important_passwords", "secret_password": "opensesame"}

       The key "secret_password" will be visible to an evesdropper, but the value "opensesame" will be protected. Both the key "id" and its  value
       "important_passwords" will be visible to an evesdropper.

       Chef Server does not provide a secure mechanism for distributing encryption keys.

SEE ALSO

       knife-search(1)

AUTHOR

       Chef was written by Adam Jacob adam@opscode.com with many contributions from the community.

DOCUMENTATION

       This  manual  page was written by Joshua Timberman joshua@opscode.com. Permission is granted to copy, distribute and / or modify this docu-
       ment under the terms of the Apache 2.0 License.

CHEF

       Knife is distributed with Chef. http://wiki.opscode.com/display/chef/Home

Chef 10.12.0							     June 2012							 KNIFE-DATA-BAG(1)