On 18.04.2013 21:00, Ken Coar wrote:
Background:
The puppetmasters are under the authority and control of a specific group
(not mine ;-) ). Client sysadmins have control over the node manifests
and, to a certain extent, can modify the puppet modules.
One of the modules (and potentially others) used by my group uses a lot
of files that may get changed frequently. Rather than embedding them
in the module' files/ tree, I would like to set up one of our group's
clients as a fileserver and have the module reference them from there
rather than from the default location (the puppetmaster).
One major advantage to doing this is that we could update the files
directly, using whatever mechanism suits our purposes best, as opposed
to treating updates as a change to the module and having to update
the module itself.
Is there any reason to use a puppet as source? You can put that on an
NFS share too and reference it by path. Or clone a git repo.
Regards, David
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
