Most
chef recipes are about installing new software including all config files. Also if they are configuration recipes they usually overwrite the whole file and provide a completely recreated configuration. When you have used
cfengine and
puppet with augtool before you'll be missing the agile editing of config files.
In cfengine2...
You could write
editfiles:
{ home/.bashrc
AppendIfNoSuchLine "alias rm='rm -i'"
}
While in puppet...
You'd have:
augeas { "sshd_config":
context => "/files/etc/ssh/sshd_config",
changes => [
"set PermitRootLogin no",
],
}
Now how to do it in Chef?
Maybe I missed the correct way to do it until now (please comment if this is the case!) but there seems to be no way to use for example augtool with chef and there is no built-in cfengine like editing. The only way I've seen so far is to use Ruby as a scripting language to change files using the Ruby runtime or to use the
Script ressource which allows running other interpreters like bash, csh, perl, python or ruby. To use it you can define a block named like the interpreter you need and add a "code" attribute with a "here doc" operator (e.g. <<-EOT) describing the commands. Additionally you specify a working directory and a user for the script to be executed with. Example:
bash "some_commands" do
user "root"
cwd "/tmp"
code <<-EOT
echo "alias rm='rm -i'" >> /root/.bashrc
EOT
end
While it is not a one-liner statement as possible as in cfengine it is very flexible. The Script resource is widely used to perform ad-hoc source compilation and installations in the community codebooks, but we can also use it for standard file editing. Finally to do conditional editing use
not_if/only_if clauses at the end of the Script resource block. See also