NAME

       chake-itamae-remote - configure chake nodes with a remote itamae

DESCRIPTION

       This  configuration  manager  will  run  itamae(1) on each remote node. This is different from the itamae
       configuration manager, which runs itamae on your workstation (the host running chake). itamae-remote will
       run itamae individually on each node, which is one order of magnitude faster. This requires itamae to  be
       installed on each node, and that will be taken care of automatically by the bootstrapping process.

CONFIGURATION

       The  itamae-remote  configuration  manager requires one key called itamae-remote, and the value must be a
       list of strings representing the list of recipes to apply to the node when converging.

           host1.mycompany.com:
             itamae-remote:
               - cookbooks/basic/default.rb
               - roles/server.rb
             service1:
               option1: "here we go"

       Any extra configuration under host1.mycompany.com 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:

           {
             "itamae": [
               "cookbooks/basic.rb",
               "roles/server.rb"
             ]
             ,
             "service1": {
               "option1": "here we go"
             }
           }

       Inside itamae recipes, you can access those values by using the node object. For example:

           template "/etc/service1.conf.d/option1.conf" do
             variables option1: node["option1"]
           end

BOOTSTRAPPING

       The bootstrapping process will make sure itamae is installed. The node hostname will be set according  to
       your chake configuration.

SEE ALSO

       ○   chake(1)

                                                  December 2023                           CHAKE-ITAMAE-REMOTE(7)