Similar setup as well:
# pwd
/etc/puppet/templates
# cat header.erb
##
#
#
# This file is centrally managed, any manual changes will be
OVERWRITTEN
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 WIL
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 existenc
On 2010-06-20 15:50, Patrick Mohr wrote:
>
> On Jun 20, 2010, at 12: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
On Jun 20, 2010, at 12: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 enfo
On 2010-06-20 15:37, 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 exi
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.
--
You received this me
