Scroll to navigation

KNIFE-EDIT(1) knife edit KNIFE-EDIT(1)

NAME

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

The knife edit subcommand is used to edit objects on the Chef server. This subcommand works similar to knife cookbook edit, knife data bag edit, knife environment edit, knife node edit, and knife role edit, but with a single verb (and a single action).

Syntax

This subcommand has the following syntax:

$ knife edit (options)


Options

This subcommand has the following options:

The configuration file to use.
The path to the chef-repo. This setting will override the default path to the chef-repo. Default: same as specified by chef_repo_path in config.rb.
The port on which chef-zero will listen.
--[no-]color
Use to view colored output.
The number of allowed concurrent connections. Default: 10.
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.
The private key that knife will use to sign requests made by the API client to the Chef server.
Use to show files in the local chef-repo instead of a remote location. Default: false.
Use to show data after a destructive operation.
The layout of the local chef-repo. Possible values: static, everything, or hosted_everything. Use static for just roles, environments, cookbooks, and data bags. By default, everything and hosted_everything are dynamically selected depending on the server type. Default: everything / hosted_everything.
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.
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.

AUTHOR

Chef

Chef 12.0