chef_client Resource
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.
Syntax
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_clienttells Chef Infra Client to use theChef::Provider::ChefClientprovider during a Chef Infra Client runnameis the name of the resource block; when thenameproperty is not specified as part of a recipe,nameis also the name of the Chef Infra Clientattributeis zero (or more) of the properties that are available for this resourceactionidentifies which steps Chef Infra Client will take to bring the node into the desired state
Actions
The chef_client resource has the following actions:
:create- (default) Use to create a chef-client.
:delete- Use to delete a chef-client.
:nothing- This resource block doesn’t act unless notified by another resource to take action. Once notified, this resource block either runs immediately or is queued up to run at the end of a Chef Infra Client run.
:regenerate_keys- Use to regenerate the RSA public key for a chef-client.
Properties
The chef_client resource has the following properties:
adminUse to specify whether Chef Infra Client is an API client.
chef_serverThe URL for the Chef Infra Server.
completeUse 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- Ruby Type: true, false | Default Value:
falseContinue running a recipe if a resource fails for any reason.
nameThe name of Chef Infra Client.
notifies- Ruby Type: Symbol, Chef::Resource\[String\]
A resource may notify another resource to take action when its state changes. Specify a
'resource[name]', the:actionthat resource should take, and then the:timerfor that action. A resource may notify more than one resource; use anotifiesstatement for each resource to be notified.If the referenced resource doesn’t exist, an error is raised. In contrast,
subscribeswon’t fail if the source resource isn’t 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,:immediatelySpecifies that a notification should be run immediately, for each resource notified.
The syntax for
notifiesis:notifies :action, 'resource[name]', :timer
output_key_formatUse to specify the format of a public key. Possible values:
pem,der, oropenssh. Default value:openssh.
output_key_pathUse to specify the path to the location in which a public key will be written.
raw_jsonChef 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_keyUse to copy a public or private key, but apply a different
formatandpassword. Use in conjunction withsource_key_pass_phraseandsource_key_path.
source_key_pass_phraseThe pass phrase for the public key. Use in conjunction with
source_keyandsource_key_path.
source_key_pathThe path to the public key. Use in conjunction with
source_keyandsource_key_pass_phrase.
subscribes- Ruby Type: Symbol, Chef::Resource\[String\]
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:actionto be taken, and then the:timerfor that action.Note that
subscribesdoesn’t 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 endIn this case the
subscribesproperty reloads thenginxservice whenever its certificate file, located under/etc/nginx/ssl/example.crt, is updated.subscribesdoesn’t make any changes to the certificate file itself, it merely listens for a change to the file, and executes the:reloadaction for its resource (in this examplenginx) when a change is detected.If the other resource doesn’t exist, the subscription won’t raise an error. Contrast this with the stricter semantics of
notifies, which will raise an error if the other resource doesn’t 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,:immediatelySpecifies that a notification should be run immediately, for each resource notified.
The syntax for
subscribesis:subscribes :action, 'resource[name]', :timer
validatorUse to specify if Chef Infra Client is a chef-validator.
Examples
This resource does not have any examples.