.\" generated with Ronn-NG/v0.9.1
.\" http://github.com/apjanke/ronn-ng/tree/0.9.1
.TH "CHAKE\-ITAMAE" "7" "December 2023" ""
.SH "NAME"
\fBchake\-itamae\fR \- configure chake nodes with itamae
.SH "DESCRIPTION"
This configuration manager will run \fBitamae(1)\fR against your nodes\.
.SH "CONFIGURATION"
The \fIitamae\fR configuration manager requires one key called \fBitamae\fR, and the value must be a list of strings representing the list of recipes to apply to the node when converging\.
.IP "" 4
.nf
host1\.mycompany\.com:
  itamae:
    \- cookbooks/basic/default\.rb
    \- roles/server\.rb
  service1:
    option1: "here we go"
.fi
.IP "" 0
.P
Any extra configuration under \fBhost1\.mycompany\.com\fR will be saved to a JSON file and given to the itamae \-\-node\-json option in the command line\. For example, the above configuration will produce a JSON file that looks like this:
.IP "" 4
.nf
{
  "itamae": [
    "cookbooks/basic\.rb",
    "roles/server\.rb"
  ]
  ,
  "service1": {
    "option1": "here we go"
  }
}
.fi
.IP "" 0
.P
Inside itamae recipes, you can access those values by using the \fBnode\fR object\. For example:
.IP "" 4
.nf
template "/etc/service1\.conf\.d/option1\.conf" do
  variables option1: node["option1"]
end
.fi
.IP "" 0
.SH "BOOTSTRAPPING"
Very little bootstrapping is required for this configuration manager, as itamae requires no setup on the node site since the Ruby code in the recipes is interpreted locally and not on the nodes\. During bootstrapping, only the node hostname will be set according to your chake configuration\.
.SH "SEE ALSO"
.IP "\[ci]" 4
\fBchake(1)\fR
.IP "" 0