locale resource¶
Use the locale resource to set the system’s locale.
New in Chef Client 14.5.
Syntax¶
The locale resource has the following syntax:
locale 'name' do
lang String # default value: en_US.utf8
lc_all String # default value: en_US.utf8
action Symbol # defaults to :update if not specified
end
where:
localeis the resource.nameis the name given to the resource block.actionidentifies which steps the chef-client will take to bring the node into the desired state.langandlc_allare the properties available to this resource.
Actions¶
The locale resource has the following actions:
:update- Updates the system’s locale.
:nothing- Define this resource block to do nothing until notified by another resource to take action. When this resource is notified, this resource block is either run immediately or it is queued up to be run at the end of the Chef Client run.
Properties¶
The locale resource has the following properties:
langRuby Type: String | Default Value:
en_US.utf8Sets the default system language.
lc_allRuby Type: String | Default Value:
en_US.utf8Sets the fallback system language.
Common Resource Functionality¶
Chef resources include common properties, notifications, and resource guards.
Common Properties¶
The following properties are common to every resource:
ignore_failureRuby Type: true, false | Default Value:
falseContinue running a recipe if a resource fails for any reason.
retriesRuby Type: Integer | Default Value:
0The number of times to catch exceptions and retry the resource.
retry_delayRuby Type: Integer | Default Value:
2The retry delay (in seconds).
sensitiveRuby Type: true, false | Default Value:
falseEnsure that sensitive resource data is not logged by the chef-client.
Notifications¶
notifiesRuby 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.A timer specifies the point during the Chef Client run at which a notification is run. The following timers are available:
:before- Specifies that the action on a notified resource should be run before processing the resource block in which the notification is located.
:delayed- Default. Specifies that a notification should be queued up, and then executed at the end of the Chef Client run.
:immediate,:immediately- Specifies that a notification should be run immediately, per resource notified.
The syntax for
notifiesis:notifies :action, 'resource[name]', :timersubscribesRuby 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
subscribesdoes 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 endIn this case the
subscribesproperty reloads thenginxservice whenever its certificate file, located under/etc/nginx/ssl/example.crt, is updated.subscribesdoes not 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.A timer specifies the point during the Chef Client run at which a notification is run. The following timers are available:
:before- Specifies that the action on a notified resource should be run before processing the resource block in which the notification is located.
:delayed- Default. Specifies that a notification should be queued up, and then executed at the end of the Chef Client run.
:immediate,:immediately- Specifies that a notification should be run immediately, per resource notified.
The syntax for
subscribesis:subscribes :action, 'resource[name]', :timer
Guards¶
A guard property can be used to evaluate the state of a node during the execution phase of the chef-client run. Based on the results of this evaluation, a guard property is then used to tell the chef-client if it should continue executing a resource. A guard property accepts either a string value or a Ruby block value:
- A string is executed as a shell command. If the command returns
0, the guard is applied. If the command returns any other value, then the guard property is not applied. String guards in a powershell_script run Windows PowerShell commands and may returntruein addition to0. - A block is executed as Ruby code that must return either
trueorfalse. If the block returnstrue, the guard property is applied. If the block returnsfalse, the guard property is not applied.
A guard property is useful for ensuring that a resource is idempotent by allowing that resource to test for the desired state as it is being executed, and then if the desired state is present, for the chef-client to do nothing.
The following properties can be used to define a guard that is evaluated during the execution phase of the chef-client run:
not_if- Prevent a resource from executing when the condition returns
true. only_if- Allow a resource to execute only if the condition returns
true.