On 2015-09-03 14:54, Felix Frank wrote:
On 03/09/2015 02:16 PM, Henrik Lindberg wrote:
It would be splendid if we could define modulepath paths with
$environment as variable part of path, like this:
modulepath = /path/to/$environment/modules
manifest = /path/to/$environment/manifest2/
Would there be any interest for this feature?
If this is implemented for modulepath setting, maybe it should be
appropriate to implement it for manifest setting too?
This scares me a bit. It looks like it has potential to open the can of
worms known as dynamic environments we managed to put the lid on with
directory environments. Will have to discuss if this can used to do
harmful things. If allowed it could only be allowed inside an absolute
path.
Agreed, there might be security implications.
I also fail to see the value in that. Do you mean to allow an
environment to extend itself to a whole different file system tree?
Wouldn't that just be horrible for organizing things?
The use case was to use one location for two master instances without
having to have two copies, and without having to have a modulepath that
includes the name of the environment (which is possible now).
Not sure that use case is worth the potential problems.
- henrik
--
Visit my Blog "Puppet on the Edge"
http://puppet-on-the-edge.blogspot.se/
--
You received this message because you are subscribed to the Google Groups "Puppet
Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-dev/mdkgbj%242b4%241%40ger.gmane.org.
For more options, visit https://groups.google.com/d/optout.
