push-jobs-client.rb
A push-jobs-client.rb file is used to specify the configuration details for the Chef Push Jobs client.
- This file is loaded every time this executable is run
- This file is not created by default
- When a
push-jobs-client.rbfile is present in the default location, the settings contained within that file will override the default configuration settings
Settings
This configuration file has the following settings:
allow_unencryptedAllow unencrypted connections to 1.x servers. Default value:
falsechef_server_url-
The URL for the Chef Infra Server. For example:
https://localhost/organizations/ORG_NAME client_keyThe location of the file that contains the client key. Default value:
/etc/chef/client.pem.file_dirThe directory for temporary files. Default value:
/tmp/chef-push.node_nameThe unique identifier of the node.
ssl_verify_mode-
Set the verify mode for HTTPS requests.
- Use
:verify_noneto do no validation of SSL certificates. - Use
:verify_peerto do validation of all SSL certificates, including the Chef Infra Server connections, S3 connections, and any HTTPS remote_file resource URLs used in a Chef Infra Client run. This is the recommended setting.
Depending on how OpenSSL is configured, the
ssl_ca_pathmay need to be specified. Default value::verify_peer. - Use
trusted_certs_dirThe location of trusted certificates. Default value:
'/etc/chef/trusted_certs'.whitelist-
A Hash that contains the whitelist used by Chef Push Jobs. For example:
whitelist { 'job-name' => 'command', 'job-name' => 'command', 'chef-client' => 'chef-client' }
© 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.
https://docs.chef.io/config_rb_push_jobs_client/