Scott, I know it defaults to production if a environment is not specified. However, that's not the case here. The client *is* specifying an environment, the server doesn't know about that environment. I think this is different than what you are describing - if the client does not specify an environment, it is totally sane/correct to pass out the "production" manifests. However, if the client specifies an environment the server doesn't know about, isn't it at least worth warning about?
--Paul On Mon, Mar 22, 2010 at 11:50 AM, Scott Smith <sc...@ohlol.net> wrote: > On 3/22/10 10:27 AM, Paul Lathrop wrote: >> >> IMHO this is a bug, but I can see how it might be by design. Any >> comments? Should I file it? >> >> --Paul >> > > Don't know if it's a bug but... Yeah it defaults to "production" - you have > to create an empty manifest for "production" in order to prevent Very Scary > Things from occuring if you happen to also have a "production" Puppet env. > > -scott > > -- > 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. > > -- 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.
