Craig Dunn

@jtopjian Firstly thanks for your work on this - it's awesome! Namespaces were initially a required thing, but as we looked at other scenarios and tooling I realized that this...

@beddari @jtopjian This is handled in #117

I've been thinking about this lately - especially after we introduced the `dig` feature into hiera-http. The issue is that the datasource expects to lookup the requested key from whatever...

Possibly I'm overthinking this - maybe just a shipped output filter called dig that will take a hash and pull out the value. Examples: ` output_filter :dig, request.namespace` ` output_filter...

#112 contains a new output filter called `dig` - This can be used to solve both your use cases above .... using your example; ``` { "class": { "param": "value"...

This doesn't quite fix your issue for the http datasource so I've reopened it - the http datasource needs the ability to not drill down into the hash and try...

@den-is let me clarify > ... the http datasource needs the ability to **not** drill down ... What I mean by that is that currently the http datasource attempts by...

Hi @hhenkel - I think this was already noted in #104 Closes #104

~~This will be developed as a third party plugin initially.~~ This will be shipped in core.

@beddari - fairly simple really, I hope.... The aim would be to lookup a series of "paths" in consul_kv much like the file datasource does with YAML files. I'm looking...