I'm looking for a way to parameterize the module path at runtime based on
multiple variables, including the environment. We've got a puppet master that
serves nodes from several different projects, each of which have their own
dev/test/prod environments. I'd like for each project to have their own entry
in the module path. This way a project could have control over multiple
modules and create new ones as they see fit, without impacting others who use
the same puppetmaster. I'm envisioning something like
/etc/puppet/modules/common:/etc/puppet/modules/$project/$environment
where $project is a fact attached to the node that's checking into the master.
This
Is this possible? Can arbitrary variables be used in the modulepath in
puppet.conf?
Thanks,
Brian
--
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.
