Open KiNgMaR opened 8 years ago
Using node-etcd "4.2.1" and etcd "2.2.3":
etcd.machines(console.log); { [Error: Key not found] errorCode: 100, error: { errorCode: 100, message: 'Key not found', cause: '/_etcd', index: 14 } } '' { 'content-type': 'application/json', 'x-etcd-cluster-id': 'xxx', 'x-etcd-index': '14', date: 'Tue, 12 Jan 2016 14:54:07 GMT', 'content-length': '72' }
After changing the URL to "machines" instead of "keys/_etcd/machines" it's working - although I don't know whether the response format still is the same. Judging from this: https://github.com/coreos/etcd/issues/1279 it changed around etcd v0.5.0.
"machines"
"keys/_etcd/machines"
Thanks for looking into it.
Using node-etcd "4.2.1" and etcd "2.2.3":
After changing the URL to
"machines"
instead of"keys/_etcd/machines"
it's working - although I don't know whether the response format still is the same. Judging from this: https://github.com/coreos/etcd/issues/1279 it changed around etcd v0.5.0.Thanks for looking into it.