How to Upload Specific File to Chef
Provided by: chef_11.eight.2-2_all 
NAME
pocketknife-upload - The man folio for the knife upload subcommand. The knife upload subcommand is used to upload roles, cookbooks, environments, and information bags to the server from the current working directory in the chef-repo. This subcommand is often used in conjunction with pocketknife diff, which tin can be used to see exactly what changes will be uploaded, and and so knife download, which does the opposite of knife upload. Common Options The following options can be run with all Knife sub-commands and plug-ins: -c CONFIG, --config CONFIG The configuration file to use. --color Indicates that colored output will be used. -d, --disable-editing Indicates that $EDITOR will not be opened; information volition be accepted as-is. --defaults Indicates that Knife will apply the default value, instead of asking a user to provide one. -e EDITOR, --editor EDITOR The $EDITOR that is used for all interactive commands. -E Environment, --environment ENVIRONMENT The proper noun of the environment. When this selection is added to a command, the command will run only confronting the named environment. -f FILE_NAME, --file FILE_NAME Indicates that the private central will be saved to a specified file name. -F FORMAT, --format FORMAT The output format: summary (default), text, json, yaml, and pp. -h, --aid Shows help for the control. -one thousand Primal, --primal Fundamental The private cardinal that Knife will use to sign requests made by the API customer to the server. --no-color Indicates that colour will not be used in the output. -p PASSWORD, --password PASSWORD The user password. --print-afterwards Indicates that information will exist shown afterwards a destructive performance. -southward URL, --server-url URL The URL for the server. -u USER, --user USER The user name used by Pocketknife to sign requests made by the API client to the server. Authentication will neglect if the user name does not friction match the private key. -v, --version The version of the chef-customer. -V, --verbose Set for more verbose outputs. Utilise -VV for maximum verbosity. -y, --yes Indicates that the response to all confirmation prompts will be "Yes" (and that Knife will not enquire for confirmation). Syntax This statement has the following syntax: $ pocketknife upload [PATTERN...] (options) Options This subcommand has the following options: --chef-repo-path PATH The path to the chef-repo. This setting volition override the default path to the chef-repo. Default: aforementioned every bit specified by chef_repo_path in config.rb. --concurrency The number of allowed concurrent connections. Default: 10. --[no-]unequal Indicates that only new and modified files will be uploaded. Set to false to upload all files. Default: true. --[no-]force Use --strength to upload roles, cookbooks, etc. even if the file in the directory is identical (by default, no Post or PUT is performed unless an actual alter would exist made). Default: --no-force. --[no-]freeze Indicates that a cookbook cannot be modified; any changes to this cookbook must be included as a new version. Simply the --forcefulness option can override this setting. Default: simulated. -n, --dry out-run Indicates that no activeness is taken and that results are simply printed out. Default: false. --[no-]purge Employ --purge to delete roles, cookbooks, etc. from the server if their corresponding files practice not be in the chef-repo. By default, such objects are left lone and Non purged. Default: --no-purge. --[no-]recurse Apply --no-recurse to disable uploading a directory recursively. Default: --recurse. --repo-style MODE The layout of the local chef-repo. Possible values: static, everything, or hosted_everything. Employ static for just roles, environments, cookbooks, and data bags. Past default, everything and hosted_everything are dynamically selected depending on the server blazon. Default: everything / hosted_everything. Examples To upload the entire chef-repo to the server, browse to the top level of the chef-repo and enter: $ knife upload or from anywhere in the chef-repo, enter: $ pocketknife upload / To upload the cookbooks/ directory to the server, browse to the top level of the chef-repo and enter: $ pocketknife upload cookbooks or from anywhere in the chef-repo, enter: $ knife upload /cookbooks To upload the environments/ directory to the server, browse to the top level of the chef-repo and enter: $ knife upload environments or from anywhere in the chef-repo, enter: $ knife upload /environments To upload an environment named "production" to the server, scan to the top level of the chef-repo and enter: $ pocketknife upload environments/production.json or from the environments/ directory, enter: $ knife upload production.json To upload the roles/ directory to the server, browse to the top level of the chef-repo and enter: $ pocketknife upload roles or from anywhere in the chef-repo, enter: $ knife upload /roles To upload all cookbooks that showtime with "apache" and vest to the "webserver" role, browse to the top level of the chef-repo and enter: $ knife upload cookbooks/apache\* roles/webserver.json Use the output of pocketknife deps to pass a command to pocketknife upload. For example: $ knife upload `knife deps nodes/*.json`
Writer
Opscode Chef xi.8.0 KNIFE-UPLOAD(i)
Source: http://manpages.ubuntu.com/manpages/trusty/man1/knife-upload.1.html
0 Response to "How to Upload Specific File to Chef"
Postar um comentário