git2consul
git2consul copied to clipboard
Error consul: kv.get: moved permanently
This is the complete error: { [Error: consul: kv.get: moved permanently] message: 'consul: kv.get: moved permanently' }
I am using the same config as the README with the same command adding the endpoint and port. I can clone the repo via git clone.
git2consul -c /tmp/git2consul.json.sample --endpoint consul.server --port 8500 { [Error: consul: kv.get: moved permanently] message: 'consul: kv.get: moved permanently' }
I am using consul 0.9.3
npm install git2consul npm WARN engine [email protected]: wanted: {"node":">= 4"} (current: {"node":"0.10.48","npm":"2.15.1"}) npm WARN engine [email protected]: wanted: {"node":">=4"} (current: {"node":"0.10.48","npm":"2.15.1"}) npm WARN engine [email protected]: wanted: {"node":">= 0.12"} (current: {"node":"0.10.48","npm":"2.15.1"}) [email protected] node_modules/git2consul ├── [email protected] ├── [email protected] ├── [email protected] ├── [email protected] ([email protected]) ├── [email protected] ([email protected]) ├── [email protected] ([email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]) ├── [email protected] ([email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]) ├── [email protected] ([email protected], [email protected]) ├── [email protected] ([email protected]) └── [email protected] ([email protected], [email protected], [email protected], [email protected], [email protected])
Well it seems that the problem is because of the short -c flag :S. Weird. If use --config-file it works. mmm. You can close this if you want, but it seems like a bug.
Cheers!
I can confirm I'm hitting this bug with Consul 1.0.6 as well