Jira (PUP-2213) Directory environments interacting poorly with puppet config face

[Joshua Partlow (JIRA)]

Title: Message Title

Joshua Partlow created an issue   Puppet / PUP-2213 Directory environments interacting poorly with puppet config face Issue Type: Bug Assignee: Unassigned Created: 10/Apr/14 5:48 PM Priority: Normal Reporter: Joshua Partlow I need to take more time to nail down what is going on here, but Nicholas Fagerlund noticed: 1) with environmentpath set in [main], puppet config print manifest modulepath --environment doesnotexist manifest = no_manifest modulepath = is picking up the default configured environment I believe. 2) with environmentpath set in [master] puppet config print manifest modulepath --environment doesnotexist manifest = /etc/puppet/manifests/site.pp modulepath = /etc/puppet/modules:/usr/share/puppet/modules environmentpath seems to be ignored and you get the default settings. 3) I'm additional noticing that with environment path set, you can still config print a legacy environment. Add Comment   This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.