This page is generated from the Chef Infra Client source code. To suggest a change, edit the chef_client.rb file and submit a pull request to the Chef Infra Client repository.
Use the chef_client resource to create clients on your Chef Infra Server from within Chef Infra cookbook code.
The syntax for using the chef_client resource in a recipe is as follows:
chef_client 'name' do
attribute 'value' # see properties section below
...
action :action # see actions section below
end
where:
chef_client tells Chef Infra Client to use the Chef::Provider::ChefClient provider during a Chef Infra Client runname is the name of the resource block; when the name property is not specified as part of a recipe, name is also the name of the Chef Infra Clientattribute is zero (or more) of the properties that are available for this resourceaction identifies which steps Chef Infra Client will take to bring the node into the desired stateThe chef_client resource has the following actions:
:create:delete:nothing:regenerate_keysThe chef_client resource has the following properties:
admin Use to specify whether Chef Infra Client is an API client.
chef_server The URL for the Chef Infra Server.
complete Use to specify if this resource defines a chef-client completely. When true, any property not specified by this resource will be reset to default property values.
ignore_failure false Continue running a recipe if a resource fails for any reason.
name The name of Chef Infra Client.
notifies A resource may notify another resource to take action when its state changes. Specify a 'resource[name]', the :action that resource should take, and then the :timer for that action. A resource may notify more than one resource; use a notifies statement for each resource to be notified.
If the referenced resource does not exist, an error is raised. In contrast, subscribes will not fail if the source resource is not found.
A timer specifies the point during a Chef Infra Client run at which a notification is run. The following timers are available:
:beforeSpecifies that the action on a notified resource should be run before processing the resource block in which the notification is located.
:delayedDefault. Specifies that a notification should be queued up, and then executed at the end of a Chef Infra Client run.
:immediate, :immediately
Specifies that a notification should be run immediately, per resource notified.
The syntax for notifies is:
notifies :action, 'resource[name]', :timer
output_key_format Use to specify the format of a public key. Possible values: pem, der, or openssh. Default value: openssh.
output_key_path Use to specify the path to the location in which a public key will be written.
raw_json Chef Infra Client as JSON data. For example:
{
"clientname": "client_name",
"orgname": "org_name",
"validator": false,
"certificate": "-----BEGIN CERTIFICATE-----\n
...
1234567890abcdefghijklmnopq\n
...
-----END CERTIFICATE-----\n",
"name": "node_name"
}
source_key Use to copy a public or private key, but apply a different format and password. Use in conjunction with source_key_pass_phrase and source_key_path.
source_key_pass_phrase The pass phrase for the public key. Use in conjunction with source_key and source_key_path.
source_key_path The path to the public key. Use in conjunction with source_key and source_key_pass_phrase.
subscribes A resource may listen to another resource, and then take action if the state of the resource being listened to changes. Specify a 'resource[name]', the :action to be taken, and then the :timer for that action.
Note that subscribes does not apply the specified action to the resource that it listens to - for example:
file '/etc/nginx/ssl/example.crt' do
mode '0600'
owner 'root'
end
service 'nginx' do
subscribes :reload, 'file[/etc/nginx/ssl/example.crt]', :immediately
end
In this case the subscribes property reloads the nginx service whenever its certificate file, located under /etc/nginx/ssl/example.crt, is updated. subscribes does not make any changes to the certificate file itself, it merely listens for a change to the file, and executes the :reload action for its resource (in this example nginx) when a change is detected.
If the other resource does not exist, the subscription will not raise an error. Contrast this with the stricter semantics of notifies, which will raise an error if the other resource does not exist.
A timer specifies the point during a Chef Infra Client run at which a notification is run. The following timers are available:
:beforeSpecifies that the action on a notified resource should be run before processing the resource block in which the notification is located.
:delayedDefault. Specifies that a notification should be queued up, and then executed at the end of a Chef Infra Client run.
:immediate, :immediately
Specifies that a notification should be run immediately, per resource notified.
The syntax for subscribes is:
subscribes :action, 'resource[name]', :timer
validator Use to specify if Chef Infra Client is a chef-validator.
This resource does not have any examples.
© 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/resources/chef_client/