Jira (PUP-7479) ENC-enforced environment makes `puppet lookup` environment simulation difficult

[Henrik Lindberg (JIRA)]

Title: Message Title

Henrik Lindberg commented on PUP-7479   Re: ENC-enforced environment makes `puppet lookup` environment simulation difficult Wrapping the configured terminus in one that does what Nick Walker suggests would solve the problem. Gary Larizza Are you saying that it is a bad idea in the first place to allow a user to specify the environment when doing a lookup, and that they must configure the ENC to allow it? Any implementation that "pokes" the CLI given environment would behave the same way. An implementation could: Add the following option to the lookup application option('--environment name') do |arg| options[:environment] = arg end And then get the node returned from the indirection: node = Puppet::Node.indirection.find(node) And then do the following override (i.e. always) node.environment = options[:environment] unless options[:environment].nil? if we need to output that the node switched env then it is difficult to get that into the actual explain output, but it could be logged to console. Add Comment   This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.