Chris Westin wrote:
> Sure, but I'm using content => template(...) to fill in the file.
> This appears in a baser class, and various other classes and defines
> are layered on top that, providing substitution variable values at
> different levels.
Problem is that some files really beg for being filled in from very
different places in the manifests. A typical example would be the
/etc/sysconfig/iptables file (in RedHat); you would normally want
the parts of your manifest that deals with configuring email to add
iptables rules for accessing the SMTP, IMAP and POP ports, while rules
for accessing the HTTP port are in the manifest parts dealing with
Apache.
> It seems unlikely that native resources could be created for all such
> possible files since there are so many packages out there that have
> their own configuration files.
That's why we have things like Augeas, defines, and custom types, so we
users of Puppet can create those resource types as we need them.
/Bellman
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
