That is what we do (and we enforce it by convention rather than technically.)
# MANAGED BY PUPPET! # /modules/foo/templates/bar.conf # ..any associated warnings, weirdness (eg template called from other module) etc On files that other groups might be touching, we add something like: # Changes WILL BE overwritten every 30 mins! Any permanent changes must be checked # into git under "foo/puppet/". On Mon, Jun 21, 2010 at 10:16 AM, Joe McDonagh <[email protected]>wrote: > On 06/20/2010 03:37 PM, Psyber wrote: > >> Anyone have any ideas on adding a default header to puppet managed >> files and templates? >> This might be tricky because of the different methods of adding >> comments for different types of files but I'm certainly open to >> suggestions that would enforce the existence of a header. >> >> >> > Generally I add in by hand, and I make sure it says whether this is managed > as a template or plain file, and what module it can be found in. > > > -- > Joe McDonagh > Operations Engineer > AIM: YoosingYoonickz > IRC: joe-mac on freenode > "When the going gets weird, the weird turn pro." > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<puppet-users%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
