Jira (PUP-2213) The environmentpath setting is ignored by puppet faces unless set in [main]

[Joshua Partlow (JIRA)]

Title: Message Title

Joshua Partlow commented on an issue   Re: The environmentpath setting is ignored by puppet faces unless set in [main] So because Puppet.base_context() loads the environmentpath in the current run mode of the application, it cannot set up directory environment loaders unless environmentpath has been set in main or in the run mode section of the app's run mode. For a puppet config call, this is user run mode, so an environmentpath set in [master] is not seen when base_context is called, and only legacy loaders are set up. Because of this, when puppet config is looking up manifest/modulepath, it request a production environment...which comes back a legacy production environment, and hence picks up the default/main manifest/modulepath settings...regardless of having specified '--section master' which has no impact on the environment loaders. This is a difficult knot to cut. Add Comment   Puppet / PUP-2213 The environmentpath setting is ignored by puppet faces unless set in [main] [~nick.fagerlund] noticed: 1) with environmentpath set in [main], {code} puppet config print manifest modulepath --environment doesnotexist manifest = no_manifest modulepath = {code} is picking up the default configured environment I believe. 2) with environmentpath set in [master] {code} puppet config print manifest modulepath --envi... 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.