Chef why run

Set to true during integration testing to speed up test cycles. Use cached cookbooks without overwriting local differences from the server. Use with caution. Useful for patching a set of cookbooks on a machine when iterating during development. Run chef-zero in socketless mode. This is the default behavior on Chef Client Replace the current run-list with the specified items. This option will not clear the list of cookbooks and related files that is cached on the node. This option will not persist node data at the end of the client run.

Make only one Chef Infra Client run and cancel interval and splay options. The location in which a process identification number pid is saved. An executable, when started as a daemon, writes the pid to the specified file. Use the graph output to help identify, and then resolve performance bottlenecks in a Chef Infra Client run.

This option:. The path to a recipe. This is typically used with the --local-mode option. The location of a recipe when it exists at a URL. Use this option only when running Chef Infra Client with the --local-mode option. The amount of time in seconds to wait for a Chef Infra Client lock file to be deleted. Default value: not set indefinite. Set to 0 to cause a second Chef Infra Client to exit immediately. A random number between zero and splay that is added to interval.

Use splay to help balance the load on the Chef Infra Server by ensuring that many Chef Infra Client runs are not occurring at the same interval. Run the executable in why-run mode, which is a type of Chef Infra Client run that does everything except modify the system.

Use why-run mode to understand why the Chef Infra Client makes the decisions that it makes and to learn more about the current and proposed state of the system. Run the Chef Infra Client in local mode. This allows all commands that work against the Chef Infra Server to also work against the local chef-repo.

A new Chef Infra Client run looks for the presence of a lock file and, if present, will wait for that lock file to be deleted. The location of the lock file can vary by platform. Local mode is a way to run the Chef Infra Client against the chef-repo on a local machine as if it were running against the Chef Infra Server.

Local mode relies on chef-zero, which acts as a very lightweight instance of the Chef Infra Server. Local mode will honor the settings in a configuration file, if desired. If the client.

This allows a normal user to run the Chef Infra Client in local mode without requiring root access. This approach to configuration management can help identify where complexity exists in the system, where inter-dependencies may be located, and to verify that everything will be configured in the desired manner.

When why-run mode is enabled, a Chef Infra Client run will occur that does everything up to the point at which configuration would normally occur. This includes getting the configuration data, authenticating to the Chef Infra Server, rebuilding the node object, expanding the run-list, getting the necessary cookbook files, resetting node attributes, identifying the resources, and building the resource collection, but does not include mapping each resource to a provider or configuring any part of the system.

For example, the service resource can be used to start a service. If a service is installed from a package, then Chef Infra Client cannot check to see if the service is running until after the package is installed. In that case, why-run mode will indicate what Chef Infra Client would do about the state of the service after installing a package. This is important because service actions often trigger notifications to other resources, so it is important to know that these notifications are triggered correctly.

This allows the Chef Infra Client to be run against the chef-repo as if it were running against the Chef Infra Server. Changed in Chef Client 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. To generate an encrypted data bag item in a JSON file for use when Chef Infra Client is run in local mode via the --local-mode option , enter:.

The current version of the standard is FIPS This will disable cryptography that is explicitly disallowed in FIPS-validated software, including certain ciphers and hashing algorithms. Any attempt to use any disallowed cryptography will cause Chef Infra Client to throw an exception during a Chef Infra Client run.

MD5 is used only to generate a unique hash identifier and is not used for any cryptographic purpose. The Chef Infra Client can be run as a daemon.

For more information about these configuration options, see the Chef Infra Client cookbook repository on github. The Chef Infra Client may need to be run with elevated privileges in order to get a recipe to converge correctly. On Microsoft Windows this can be done by running the command prompt as an administrator.

On Linux, the following error sometimes occurs when the permissions used to run the Chef Infra Client are incorrect:. This requires super user privileges and, as such, is not a recommended approach. On Microsoft Windows, running without elevated privileges when they are necessary is an issue that fails silently. It will appear that Chef Infra Client completed its run successfully, but the changes will not have been made.

When this occurs, do one of the following to run Chef Infra Client as the administrator:. Log in to the administrator account. Run Chef Infra Client process from the administrator account while being logged into another account. Run the following command:. Open a command prompt by right-clicking on the command prompt application, and then selecting Run as administrator. After the command window opens, Chef Infra Client can be run as the administrator.

In large, distributed organizations the ability to modify the configuration of systems is sometimes segmented across teams, often with varying levels of access to those systems. For example, core application services may be deployed to systems by a central server provisioning team, and then developers on different teams build tooling to support specific applications. In this situation, a developer only requires limited access to machines and only needs to perform the operations that are necessary to deploy tooling for a specific application.

The default configuration of the Chef Infra Client assumes that it is run as the root user. This affords the Chef Infra Client the greatest flexibility when managing the state of any object. However, the Chef Infra Client may be run as a non-root user—i. When the Chef Infra Client is run as a non-root user the Chef Infra Client can perform any action allowed to that user, as long as that action does not also require elevated privileges such as sudo or pbrun.

Attempts to manage any object that requires elevated privileges will result in an error. There's no way to tell in why-run when you don't have a package installed which service provider is going to be required.

There's no way to know which one is correct:. In Chef Since guessing the correct thing in why-run mode is undefined, since the default provider in Ubuntu Sorry, something went wrong. Also I'm pretty sure its the Upstart provider, which inherits that line from the Simple provider:. Skip to content.

Star 6. New issue. Jump to bottom. Chef Labels Type: Bug. Copy link. Yeah this changed by design in Chef 12, this is not a bug. Sign up for free to subscribe to this conversation on GitHub.