Jira (PUP-6400) lookup cli has no way to set arbitrary scope values

[Josh Cooper (Jira)]

Title: Message Title

Josh Cooper commented on PUP-6400   Re: lookup cli has no way to set arbitrary scope values Coming back to this. It is currently possible to override the certname trusted fact by specifying the certname option: $ cat /home/josh/.puppetlabs/etc/code/environments/trusted/hiera.yaml   --- version: 5 hierarchy:   - name: "Environment"     paths:     - "%{trusted.certname}" $ cat /home/josh/.puppetlabs/etc/code/environments/trusted/data/foo.com --- key: 42 $ bundle exec puppet lookup key -E trusted --certname foo.com           --- 42 It is also possible to specify facts that are used to derive the "certname" (though if you specify one value, then you have to specify all of them: $ cat facts.json                                                        {    "hostname": "foo",   "domain": "com",   "fqdn": "foo.com",   "clientcert": "foo.com" } $ bundle exec puppet lookup key -E trusted --facts facts.json  --- 42 But you cannot specify arbitrary trusted facts nor can you specify node parameters. It would be fairly trivial to add command line options to support those use cases. Add Comment   This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.136438.1465556167000.39028.1653761340039%40Atlassian.JIRA.