I do not want to assume anything about how others use tools that are given to them. What I do know is that I like tools that provide flexibility and can be adapted to my needs. This particular case here is something that feels quite natural, especially if you consider how much code needs to be changed to achieve greater flexibility. I think we are not talking major changes here, merely desinhibition.
Come to think about it again, it would actually make more sense to create something which is similar to what ENC does for nodes. Therefore, I propose: EEL - External Environment Locator Proposed new master setting: environment_terminus = /path/to/external/environment/locator.sh It takes one argument: - requested environment name (once node and ENC agree on node environment) It returns one path to directory or file: - if what is returned is a directory, that is used as environment path - if what is returned is a file, then that is treated as path to environment.conf After that, all the normal rules apply. Maybe I should spin this into a separate thread;) B. -- 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/2255e1c6-1592-479c-b687-5cc3a8792cd2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
