Oh Ok, so what you are looking for is more like a feature to let you know that the environment "foo" does not exist.
Does not sounds bad to me, if somebody uses tons of environments it will reduce errors or at least will be easier to find them. On Mon, Mar 22, 2010 at 11:14 AM, Paul Lathrop <paul.lath...@gmail.com>wrote: > Tony, > > Sure, I understand that, but if the client is asking for a specific > environment that the puppetmaster doesn't know about, I feel like that > warrants a warning at minimum, probably an error and a refusal to > compile. Would be interested if anyone has a counter-argument. > > --Paul > > On Mon, Mar 22, 2010 at 10:59 AM, Tony G. <tony...@gmail.com> wrote: > > Hi Paul, > > > > How does your config file look like in the main section? > > > > There is a default one if no environment is defined, e.g. > > > > environments = production,testing,development > > manifest = /opt/puppet/production/site.pp <-- These are the > > modulepath = /opt/puppet/production/modules <-- default locations > > > > [production] > > manifest = /opt/puppet/production/site.pp > > modulepath = /opt/puppet/production/modules > > > > [testing] > > manifest = /opt/puppet/testing/site.pp > > modulepath = /opt/puppet/testing/modules > > > > [development] > > manifest = /opt/puppet/development/site.pp > > modulepath = /opt/puppet/development/modules > > > > > > On Mon, Mar 22, 2010 at 10:27 AM, Paul Lathrop <p...@tertiusfamily.net> > > wrote: > >> > >> Over the weekend we noticed an interesting and unexpected behavior > >> with environments. I made a change to the way our puppet.conf file is > >> generated and distributed, which led to an environment which had been > >> defined on a puppetmaster being no longer defined in puppet.conf. > >> We'll call this the "core" environement. When clients checked in and > >> asked for the "core" environment, the puppetmaster didn't know about > >> it. I would have expected an error at this point. However, what > >> happened instead was the puppetmaster passed out the configs for the > >> "production" environment without complaint. > >> > >> IMHO this is a bug, but I can see how it might be by design. Any > >> comments? Should I file it? > >> > >> --Paul > >> > >> -- > >> You received this message because you are subscribed to the Google > Groups > >> "Puppet Users" group. > >> To post to this group, send email to puppet-us...@googlegroups.com. > >> To unsubscribe from this group, send email to > >> puppet-users+unsubscr...@googlegroups.com<puppet-users%2bunsubscr...@googlegroups.com> > . > >> For more options, visit this group at > >> http://groups.google.com/group/puppet-users?hl=en. > >> > > > > > > > > -- > > Tony > > > > -- > > You received this message because you are subscribed to the Google Groups > > "Puppet Users" group. > > To post to this group, send email to puppet-us...@googlegroups.com. > > To unsubscribe from this group, send email to > > puppet-users+unsubscr...@googlegroups.com<puppet-users%2bunsubscr...@googlegroups.com> > . > > For more options, visit this group at > > http://groups.google.com/group/puppet-users?hl=en. > > > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-us...@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com<puppet-users%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > > -- Tony -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
