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

[Dominic Cleal (JIRA)]

Title: Message Title

Dominic Cleal commented on an issue   Re: puppet apply --modulepath not respected when /etc/puppet/environments/production exists It seems the way Puppet::Environments works with multiple environment loaders is part of the cause here, since it will prefer (via the "combined" loader) environments defined via environmentpath over those defined via the settings system. Since --modulepath on the command line is inherited through the settings system, this means the environmentpath always take precedence if the environment is known. Setting --environment foobar is a workaround, since you're then specifying an environment that's unknown to the environmentpath loader, but it'll fallback to the modulepath specified via --modulepath/settings. 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.