Bryan Andrews

+1 here. Airplay speaker support would be amazing.

lookup_http was installed with /opt/puppetlabs/puppet/bin/gem but I don't know exactly where it was placed in the /opt/puppetlabs path. puppetserver couldn't find it on hiera lookups though. After I manually copied...

I'm running 2015.2.0 and these are the only gem's I have: ``` [root@puppet: bandrews]# find /opt -name gem /opt/puppetlabs/puppet/bin/gem /opt/puppetlabs/server/apps/puppetserver/cli/apps/gem [root@puppet: bandrews]# ``` ``` [root@puppet: bandrews]# /opt/puppetlabs/server/apps/puppetserver/cli/apps/gem help /opt/puppetlabs/server/apps/puppetserver/cli/apps/gem: line...

I just copied your example and that worked. I think you're right but since I already got it working with a manual copy I can't verify but I bet that...

--explain output example: > URI "http://localhost:5984/configuration/companya%2Fcompanya-dev-03" > Original uri: "http://localhost:5984/configuration/%{ec2_tag_company}%2F%{ec2_tag_name}" > No such key: "profiles::jvm::default" > Returning cached value for /configuration/companya%252Fcompanya-dev-03 > It looks like the URI is correct. I...

Curl example showing the URI works: > curl http://localhost:5984/configuration/companya%2Fcompanya-dev-03 > {"_id":"companya/companya-dev-03","_rev":"1-9657c4f470e52e081f3d19eec20f269b","profiles::jvm::default":8}

I have confirmed that '%2F' in the URI is being translated to '%252F' by looking at the CouchDB access logs which is why it fails.

We really need this to be useful. The old API token is gone and URL's are used instead now. So +1 vote here

I have ran into the same problem