| As a user of Puppet, I would like to ability for puppet lookup to return information about where a particular key was found. As I would like to know the path of where the key was found, I used the --explain flag, however, the bulk of the output is where things aren't found. As I have a large Puppet implementation, this can often mean scrolling through many lines of "not found" data to find the information about where the key was found and what it's path was. It would be nice if there was a flag (.e.g --explain-brief?) that only reported information about where the key was found and suppressed any information about where it was not found. As a user of puppet lookup, I generally only care about where a key is found and the associated path / location information for that particular key. Please see an example of the puppet lookup result reporting multiple instances of "not found" below: Path: "/etc/puppetlabs/code/environments/common_nonprod/hieradata/app_id/ibok.yaml"
Original path: "common_%{::pce_environment}/hieradata/app_id/%{::app_id}.yaml"
Path not found
Path: "/etc/puppetlabs/code/environments/common_nonprod/hieradata/pce_environment/nonprod.yaml"
Original path: "common_%{::pce_environment}/hieradata/pce_environment/%{::pce_environment}.yaml"
Path not found
...
(This type of output continues for many lines / screens of text as --explain iterates through the hierarchy) Example desired command line interaction: puppet lookup myinfo::to_lookup --node mynodename.org --environment myenvironment --explain-brief Found key: myinfo::to_lookup value: "Thisisthevalue::IFound" |
