breser / git2consul

Mirrors the contents of a git repository into Consul KVs.
Other
762 stars 164 forks source link

Error consul: kv.get: moved permanently #164

Open aroca opened 7 years ago

aroca commented 7 years ago

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 request@2.79.0: wanted: {"node":">= 4"} (current: {"node":"0.10.48","npm":"2.15.1"}) npm WARN engine esprima@4.0.0: wanted: {"node":">=4"} (current: {"node":"0.10.48","npm":"2.15.1"}) npm WARN engine form-data@2.1.4: wanted: {"node":">= 0.12"} (current: {"node":"0.10.48","npm":"2.15.1"}) git2consul@0.12.13 node_modules/git2consul ├── rimraf@2.2.8 ├── properties@1.2.1 ├── underscore@1.8.3 ├── consul@0.10.0 (papi@0.15.0) ├── mkdirp@0.5.0 (minimist@0.0.8) ├── express@4.6.1 (merge-descriptors@0.0.2, utils-merge@1.0.0, parseurl@1.1.3, finalhandler@0.0.3, cookie-signature@1.0.4, range-parser@1.0.0, fresh@0.2.2, vary@0.1.0, qs@0.6.6, media-typer@0.2.0, methods@1.1.0, cookie@0.1.2, escape-html@1.0.1, serve-static@1.3.2, buffer-crc32@0.2.3, depd@0.3.0, path-to-regexp@0.1.3, debug@1.0.3, proxy-addr@1.0.1, type-is@1.3.2, accepts@1.0.7, send@0.6.0) ├── body-parser@1.4.3 (qs@0.6.6, media-typer@0.2.0, bytes@1.0.0, raw-body@1.2.2, depd@0.3.0, type-is@1.3.1, iconv-lite@0.4.3) ├── js-yaml@3.10.0 (esprima@4.0.0, argparse@1.0.9) ├── bunyan@1.1.3 (mv@2.1.1) └── coveralls@2.13.3 (log-driver@1.2.5, minimist@1.2.0, lcov-parse@0.0.10, js-yaml@3.6.1, request@2.79.0)

aroca commented 7 years ago

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!

jensendw commented 6 years ago

I can confirm I'm hitting this bug with Consul 1.0.6 as well