weave
module · Code & DevOps

Chef

Chef Infra Server — nodes, cookbooks, environments, runs

Namespace: weave chef Env: CHEF_SERVER_URL
5
Commands
1
State kinds
Code & DevOps
Category
1
API docs

Setup

Configure credentials via environment variables. We recommend sourcing them through 1Password or your secrets manager rather than committing them to the shell rc.

Official API reference

weave commands for this module are checked against the vendor's published API.

Variable Description Status
CHEF_SERVER_URLRequired for authentication.required
CHEF_CLIENT_NAMERequired for authentication.required
CHEF_KEY_FILERequired for authentication.required

Sanity-check the wiring:

weave secrets check
weave chef --help
weave doctor   # reports CHEF_SERVER_URL status

Capabilities

What this module can do, by entity and verb. means a working CLI surface; · means not (yet) wired.

Entity findlistshowdosnapshotdiffapply
cookbook······
environment······
node·····
resources····
run······

Commands

Every registered CLI command, grouped by verb. Each example uses placeholder arguments — substitute real values for your environment.

find (1)

find node

read

Find a Chef node by name.

weave chef find node <name>

list (4)

list cookbooks

read

List cookbooks.

weave chef list cookbooks <arg>

list environments

read

List environments.

weave chef list environments <arg>

list nodes

read

List Chef nodes.

weave chef list nodes <arg>

list runs

read

List recent Chef client runs.

weave chef list runs <arg>
snapshot / diff / apply are generated automatically from the State Kinds declared on this module — see the State kinds section below for per-kind details. Workflow: snapshot → edit YAML → diffapply --yes (or confirm interactively; apply --dry-run previews the same diff).

State kinds

Resources this module can snapshot and diff; apply where the kind supports live writes (see Round-trip per kind). Always run diff before apply; use --yes in automation after review. Files live under .weave-state/chef/.

This module is on the thinner integration path — use snapshot / diff for audit; confirm apply per kind below before relying on writes.

resources

snapshot diff apply

chef resources — field-level apply via REST.

Scope
Round-trip
Full round-trip — snapshot, diff, apply.

State file skeleton

module: chef
kind: resources
items:
  - # <fields specific to this kind — see snapshot output>

Workflows

End-to-end recipes from operators who already run this module in production. Copy, adapt, and put under change-control.

Resources audit

Snapshot and diff resources.

weave chef snapshot resources
$EDITOR .weave-state/chef/resources.yaml
weave chef diff resources
weave chef apply resources

Terraform parity

For each Terraform resource in the canonical provider, here's the equivalent live-API verb in weave. Use this as a migration cheat-sheet, not a 1:1 contract — weave deliberately stays in the live-state lane, not the desired-state lane.

Terraform resource weave equivalent
chef_resourcesweave chef snapshot/diff/apply resources
Snapshot/diff for audit; confirm apply on the module page.

Troubleshooting & source

Missing credentials

Run weave doctor — it reports which env vars (including CHEF_SERVER_URL) are set and which are blank.

Unexpected behaviour from a state apply

Re-run weave chef diff <kind> to confirm the controller's current state, then re-snapshot before the next apply. The driver always re-snapshots before diffing.