A Chef recipe is an ordered sequence of procedural configuration steps. The Chef client executes those steps in order to bring a managed device toward its desired state. section 25.2.3
Chef uses Ruby and an agent-based pull model: a Chef client installed on each managed device connects to the Chef server and retrieves current configuration. section 25.2.3
Key relationships:
- Groups recipes into cookbooks, which may also contain templates, files, and metadata. section 25.2.3
- Contrasts with Puppet’s declarative approach by specifying the actions and sequence required for configuration. section 25.2.3
- Fits organizations that prefer pull-based configuration management and support a Chef agent on managed devices. section 25.2.3
