Using the 0.2.2 release, any attempts to backup the entire KV store failed to find any keys. Examining strace output from this process revealed that the api URL is "GET /v1/kv//?consistent=&recurse=". These URLs lead to redirects.
There is a fix that went into Consul API a few weeks after the 0.2.2 release that avoids a API redirect by removing the trailing slash from the key:
hashicorp/consul@8c3db1c
I downloaded consul-snapshot source and recompiled after patching the vendored consul/api to match, and using that build, the KV backup worked.
Is it possible to create a new release compiled against the newer version of the Consol API ? I believe that will fix this problem.
Using the 0.2.2 release, any attempts to backup the entire KV store failed to find any keys. Examining strace output from this process revealed that the api URL is "GET /v1/kv//?consistent=&recurse=". These URLs lead to redirects.
There is a fix that went into Consul API a few weeks after the 0.2.2 release that avoids a API redirect by removing the trailing slash from the key:
hashicorp/consul@8c3db1c
I downloaded consul-snapshot source and recompiled after patching the vendored consul/api to match, and using that build, the KV backup worked.
Is it possible to create a new release compiled against the newer version of the Consol API ? I believe that will fix this problem.