 chef_data_bag Resource   Edit this page in the Chef repository 
  This page is generated from the Chef Infra Client source code. To suggest a change, edit the chef_data_bag.rb file and submit a pull request to the Chef Infra Client repository.   All Infra resources page   Data bags store global variables as JSON data. Data bags are indexed for searching and can be loaded by a cookbook or accessed during a search.  Use the chef_data_bag resource to manage data bags. Syntax 
The syntax for using the chef_data_bag resource in a recipe is as follows: chef_data_bag 'name' do
  attribute 'value' # see properties section below
  ...
  action :action # see actions section below
end
 where:  
chef_data_bag tells Chef Infra Client to use the Ch8b7c:f320:99b9:690f:4595:cd17:293a:c069Provider8b7c:f320:99b9:690f:4595:cd17:293a:c069hefDataBag provider during a Chef Infra Client run 
name is the name of the resource block and also the name of the data bag 
attribute is zero (or more) of the properties that are available for this resource 
action identifies which steps Chef Infra Client will take to bring the node into the desired state  Actions  The chef_data_bag resource has the following actions:  :create Default. Use to create a data bag. :delete Use to delete a data bag. :nothing This resource block does not 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.  Properties  The chef_data_bag resource has the following properties:   chef_server   The URL for the Chef Infra Server.     ignore_failure   Ruby Type: true, false | Default Value: false Continue running a recipe if a resource fails for any reason.     name   The name of the data bag.     notifies   Ruby Type: Symbol, Ch8b7c:f320:99b9:690f:4595:cd17:293a:c069Resource\[String\] 
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:  :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 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
     subscribes   Ruby Type: Symbol, Ch8b7c:f320:99b9:690f:4595:cd17:293a:c069Resource\[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 :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:  :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 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
   Examples  This resource does not have any examples.  

    
{'path': 'public/docs/chef~18/resources/chef_data_bag/index.html', 'source': 'DevDocs.IO'}