Jira (PUP-8220) Handle lookup CLI "trusted" in a better way

[Gerhardus Geldenhuis (JIRA)]

Title: Message Title

Gerhardus Geldenhuis commented on PUP-8220   Re: Handle lookup CLI "trusted" in a better way Users will be stupid... as in it is very likely that someone ( me probably ) will specify facts for the trusted hash that is different from what it would have been had it been computed. I personally view puppet lookup --facts <file> as a debug tool and if I do something stupid in it I will see strange behaviour. Perhaps a warning or notice might be in order if you do something like that. My original intend was to use puppet lookup as a tool to verify my hiera hierarchy is working and supplying the right data. Since we use a number of trusted facts (extended trusted facts ) as part of our hierarchy being able to specify these trusted facts in a debug situation is very useful. We don't currently have PuppetDB configured so those facts can't be obtained by puppet lookup. However I don't want to be relying on puppetdb either and need to pre-emptively test the hierarchy for correct fact lookup. Add Comment   This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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.