etcdctl get option for escaping unprintable bytes

[vorburger]

During local testing, I've used etcdctl ls -r just wanting to see if it "had any entries" (and perhaps like wc -l them), and realized, after some confusion, that etcdctl ls seems to just silently skip any keys with unprintable characters?

Perhaps it could instead (have an option to) print them with some sort of escaping.

See also etcd-io/jetcd#399.

[hexfusion]

Hi @vorburger for v3 we use something like ETCDCTL_API=3 etcdctl get --from-key '' does this output as expected? My understanding is that jetcd is the official java client for etcd v3 so this would be a more proper comparison.

[hexfusion]

For just keys ETCDCTL_API=3 etcdctl get --from-key '' --keys-only

[vorburger]

@hexfusion indeed using ETCDCTL_API=3 etcdctl get --from-key '' instead of etcdctl ls -r prints all.

It's "binary" though.. but I guess one could pipe it into some suitable tool - e.g. ETCDCTL_API=3 etcdctl get --from-key '' | od -c, although that is far more verbose than some kind of simpler "KV-per-line with any non-printable characters escaped" kind of output format, as proposed in etcd-io/jetcd#399. BTW, for any external UNIX piped utility it's probably not possible to distinguish separate KVs from CR/LF bytes in keys and values.

PS: Shouldn't ETCDCTL_API=3 become the default at some point?

[hexfusion]

PS: Shouldn't ETCDCTL_API=3 become the default at some point?

Yes sir, v3.4 #9600

[hexfusion]

It's "binary" though.. but I guess one could pipe it into some suitable tool

We also have --hex flag. etcdctl get --from-key '' --hex

Do you have any further questions? Could you give an example of problematic data?

[vorburger]

Let's close this (the --hex is good enough).