Jira (PUP-1765) puppet apply --modulepath not respected when /etc/puppet/environments/production exists

[Joshua Partlow (JIRA)]

Title: Message Title

Joshua Partlow commented on an issue   Re: puppet apply --modulepath not respected when /etc/puppet/environments/production exists Merged to master in 937613a. For functional review, there are several test cases explicitly covered in the acceptance and integration spec for this pr that illustrate the basic issue of how commandline manifest/modulepath settings interact with various puppet applications. But there might be other cases, or maybe these cases don't make sense? It basically comes down to what it means to override one or both of these settings for various puppet faces using various environments...particularly default directory environments. Add Comment   Puppet / PUP-1765 puppet apply --modulepath not respected when /etc/puppet/environments/production exists This appears to be a strange condition since the new directory environments work went in. When /etc/puppet/environments/production exists, puppet apply stops obeying --modulepath and instead attempts to look up the module in /etc only. For example: {noformat} # mkdir /etc/puppet/environments/production # puppet module install -i /tmp/test saz/ntp ... 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/groups/opt_out.