> How would the command line work relative to external nodes? > > 1) command line > 2) external nodes > 3) facts > 4) config file > 5) server-side default > > ? > > This is, um, heinous and hideous. Do we really need that much > flexibility in how people use environments? Is there some way we can
I currently use environments like this spread over various clients: - command line, yes cos there's no other way to do 'do this stuff first' than with an environment, or developers want to just test something on a box and add --environment to the command line, very helpful, I sometimes also just do export FACTER_environment=foo first - external nodes, we all know why - facts, very useful, I have machines determining their environment based on their ip address - config file, i dont really use it except to put my nodes in my bootstrap node at kickstart time - see cli usage - server-side default I'd consider this a nice to have, because i wouldnt bother with the config file for my bootstrapping I'd just put everything that isnt otherwise configured into a server controlled default > rethink the problem a bit and come up with something cleaner? so towards this, I listed my use cases for all of the above, maybe it will help someone think of a less insane solution :) -- 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 -~----------~----~----~----~------~----~------~--~---
