chef-run (executable) - Tool

Specifying resource properties and actions

In the command line, you can specify any of the Chef Infra resources. The resource type, the resource name, and the chef-run command should all be entered in that order. 

Consider this:

chef-run host1 group awesome_group

This command designates the awesome group resource for the group. Use a key=value syntax to specify actions and properties:

chef-run host1 group awesome_group gid=1001
chef-run host1 user super_person gid=1001 'password=complex=p@ssword!!'
chef-run host1 user super_person action=remove

Running a Recipe

Specify a recipe using its path in order to run it completely:

chef-run host1 /path/to/recipe.rb
chef-run host1 recipe.rb

You can also mention the cookbook if your recipe is in one:

chef-run host1 /cookbooks/my_cookbook/recipes/default.rb
chef-run host1 /cookbooks/my_cookbook

Chef-run will run the default recipe from the cookbook on the target node if the cookbook's path is specified.

Chef-run offers the option to look up your cookbook in a nearby library. Assuming your cookbook repository is located at /cookbooks, run: cd /cookbooks

chef-run host1 my_cookbook
chef-run host1 my_cookbook::non_default_recipe

Chef-run is instructed to use an alternative recipe via the command::recipe name. /.chef-workstation/config.toml and /.chef/config.rb are the local Chef Workstation and Chef configuration files that are read by chef-run. It searches the paths listed in both files for cookbooks.

Configuring Cookbook Dependencies and Sources

Chef-run generates a Policyfile bundle that contains the specified cookbook when a target node is convergent. This will be recognized if the cookbook you mentioned contains a separate Policyfile. rb.

Your metadata.rb file contains: name "really_complicated"

…
depends "pretty_simple"
In your Policyfile. rb file:
name "really_complicated"
default_source :supermarket
default_source :chef_repo, "../"
run_list "really_complicated::first"
cookbook "pretty_simple"
In your recipes/first.rb
log "lets include some stuff"
include_recipe "pretty_simple::second"

In order to prepare the target node for convergence, chef-run host1 really complicated::first gathers all the cookbook requirements (pretty simple) first. The first recipe launches its second recipe after determining its local dependency on the pretty simple cookbook when it is executing on that node.

Frequently Asked Questions

What characteristics does Chef Compliance have?

By using standardized audit and remediation material across heterogeneous estates to enable visibility and control across hybrid and multi-cloud environments, Chef Compliance helps enforce and manage compliances and avoid security incidents.

How does the DevOps team use Chef Infra for infrastructure management?

Chef Infra automates infrastructure configuration, ensures that configuration policy is consistent, accurate, adaptable, testable, versionable, and human-readable, and ensures that every configuration change will be applied uniformly throughout the whole infrastructure.

Describe the characteristics of Chef Habitat.

Regardless of the deployment platform or operating system, it delivers automation for defining, packaging, and delivering applications to any environment. Without reworking or rewriting, it produces deployable artifacts for virtual machines or containers. Additionally, it facilitates the widespread adoption of agile delivery techniques in both operations and development.

Conclusion

In this blog, we discussed the chef run executable. We also saw Specifying resource properties and actions, applying a Resource to a Single Node over SSH and over WinRM, and running a recipe. We also discussed Configuring Cookbook Dependencies and Sources. 

For more content, Refer to our guided paths on Coding Ninjas Studio to upskill yourself.
Check out this problem - Largest BST In Binary Tree

Do upvote our blogs if you find them helpful and engaging!

Happy Learning!