----- "Markus Roberts" <[email protected]> wrote:
> > So one thought, what if there were one (and only one) place to get > the > > environment but the value could optionally be an > > expression/lambda/special token of some sort that would pull the > value > > from some other (specified) location? > > > > That gets rid of the whole issue of what-trumps-what, or at least > > sidelines it; we may still want some sources (e.g. the command line) > > to take precedence but we don't have to sort a long list of sources > > based on a whole slew of use cases. > > > > * Does that sound reasonable? > > * Where should the one-true-place be? > > * Is the command line (for interactive use) the only thing that > should > > best it? > > * Are there any use cases that this wouldn't handle? > > sounds plausible but abstract, can you show some kind of potential use > case or something so we can have an idea of what you're thinking? > > > *laugh* It was intentionally abstract, because I wanted to know what > _you_ were thinking. But since you asked, here are two concrete > strawman examples: > > 1. The environment comes from the client's conf file, unless > overridden by the command line. Normally, this is a literal string > value, but it could be one of several special values such as > "!!FACT[fact name]" or "!!NODE_TOOL" or some such. If one of these is > used the appropriate action is taken to resolve the host name. ok, i can dig that > 2. The environment is always determined by facter. Facter has the > ability to get the information from various places, such as the client > config, the node manager (by templating the fact or some other such > ruse), and so forth. not a fan of this, not cos its bad, but because the barrier to entry is huge - people need to learn a whole lot of rather arcane stuff about facts and pluginsync and ruby and so forth and so on to unlock environments -- R.I.Pienaar --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en -~----------~----~----~----~------~----~------~--~---
