Hello.
I'd like to enhance the classical package/configuration/service pattern
with an additional stage: configuration syntax checking. The goal is to
ensure a service won't be restarted with an invalid configuration first,
but also to ensure this configuration error will get explicitly
notified, not just buried in logs (we use nagios for this).
In CFengine, it was quite easy to use the result of an external command
execution to position a class in case of success:
srv_dhcp.dhcpd_restart::
"/usr/sbin/dhcpd -t /etc/dhcpd.conf" define=dhcpd_config_ok
srv_dhcp.dhcpd_restart.dhcpd_config_ok::
"$(service) dhcpd restart"
srv_dhcp.dhcpd_restart.!dhcpd_config_ok::
"$(notify) dhcp-config 2 'invalid dhcp configuration'"
In Puppet documentation, I couldn't find how to use the result of an
'exec' resource to do something similar. There is an 'returns'
parameter, defining expected returns code, and the documentation
mentions triggering an error when the result differs, but I couldn't
find documentation about how to use this behavior to trigger different
actions.
--
BOFH excuse #258:
That's easy to fix, but I can't be bothered.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
