I understand the evils of the environment fallback that was previously in puppet (where all environments were promoted to 'production' if they weren't configured in puppet's configuration), however the current design I'm thinking could benefit from it.
Would it be sensible to be able to restore the previous behaviour (or better yet a 'default' named environment) via an opt-in configuration flag? With a giant caveat in the documentation of course that explains how exactly this will bite you in the ass. -- 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/30c3c4c9-3fa4-412b-99de-243a1ea98834%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
