A solo.rb file is used to specify the configuration details for chef-solo.
- This file is loaded every time this executable is run
- The default location in which chef-solo expects to find this file is
/etc/chef/solo.rb; use the
--configoption from the command line to change this location
- This file is not created by default
- When a
solo.rbfile is present in this directory, the settings contained within that file will override the default configuration settings
This configuration file has the following settings:
A 3rd-party formatter. (See nyan-cat for an example of a 3rd-party formatter.) Each formatter requires its own entry.
The location in which checksum files are stored. These are used to validate individual cookbook files, such as recipes. The checksum itself is stored in the Chef Infra Server database and is then compared to a file in the checksum path that has a filename identical to the checksum.
The Chef Infra Client sub-directory for cookbooks. This value can be a string or an array of file system locations, processed in the specified order. The last cookbook is considered to override local modifications.
The location from which a data bag is loaded. Default value:
The name of the environment.
The path to the environment. Default value:
The location in which backup files are stored. If this value is empty, backup files are stored in the directory of the target file. Default value:
The location in which cookbooks (and other transient data) files are stored when they are synchronized. This value can also be used in recipes to download files with the remote_file resource.
The path to a file that contains JSON data.
The location of the Chef Infra Client lock file. This value is typically platform-dependent, so should be a location defined by
file_cache_path. The default location of a lock file should not on an NF mount. Default value: a location defined by
The level of logging to be stored in a log file. Possible levels:
The location of the log file. Default value:
Run the Ohai plugins for name detection and resource/provider selection and no other Ohai plugins. Set to
trueduring integration testing to speed up test cycles.
The unique identifier of the node.
The URL location from which a remote cookbook tar.gz is to be downloaded.
The time (in seconds) after which an HTTP REST request is to time out. Default value:
The location in which role files are located. Default value:
The amount of time (in seconds) to wait for a Chef Infra Client lock file to be deleted. A Chef Infra Client run will not start when a lock file is present. If a lock file is not deleted before this time expires, the pending Chef Infra Client run will exit. Default value: not set (indefinite). Set to
0to cause a second Chef Infra Client to exit immediately.
The location in which cookbook files are stored (temporarily) during upload.
Run Chef Infra Client in chef-solo mode. This setting determines if Chef Infra Client is to attempt to communicate with the Chef Infra Server. Default value:
All files in a cookbook must contain valid Ruby syntax. Use this setting to specify the location in which knife caches information about files that have been checked for valid Ruby syntax.
The file mode creation mask, or umask. Default value:
Set the log level. Options:
false. When this is set to
false, notifications about individual resources being processed are suppressed (and are output at the
:infologging level). Setting this to
falsecan be useful when a Chef Infra Client is run as a daemon. Default value:
Using Chef Automate Data Collector
This example solo.rb file uses the
data_collector settings to send data to an available Chef Automate system. Since Chef Automate generates a self-signed SSL certificate by default, you will need to add the certificate (located under
/var/opt/delivery/nginx/ on the Chef Automate server) to your
trusted_certs_dir directory, as seen in this example:
data_collector.token = "YOURTOKEN"
You can run it like this
chef-solo -c solo.rb
A sample solo.rb file that contains all possible settings (listed alphabetically):