{"id":457,"date":"2009-07-30T17:51:47","date_gmt":"2009-07-30T16:51:47","guid":{"rendered":"http:\/\/wp.devco.net\/?p=457"},"modified":"2009-10-09T13:57:33","modified_gmt":"2009-10-09T12:57:33","slug":"what_does_puppet_manage_on_a_node","status":"publish","type":"post","link":"https:\/\/www.devco.net\/archives\/2009\/07\/30\/what_does_puppet_manage_on_a_node.php","title":{"rendered":"What does puppet manage on a node?"},"content":{"rendered":"
Sometimes it’s nice to try and figure out what resources of a machine are being managed by puppet. Puppet keeps a state file in either YAML or Marshall format called localconfig.yaml<\/i> it’s full of useful information, I wrote a quick script to parse it and show you what’s being managed.<\/p>\n
Typical output is:<\/p>\n
Classes included on this node:
nephilim.ml.org
common::linux
<snip><\/p>\nResources managed by puppet on this node:
service{smokeping: }
defined in common\/modules\/smokeping\/manifests\/service.pp:6<\/p>\nfile{\/etc\/cron.d\/mrtg: }
defined in common\/modules\/puppet\/manifests\/init.pp:201
<snip><\/p><\/blockquote>\nIt will show all classes and all resources including where in your manifests the resource comes from. Unfortunately for resources created by defines it shows the define as the source but I guess you can’t have it all.<\/p>\n