Add support for etcd authentication about libkv HOT 2 CLOSED

Hi @seiffert, thanks for opening the issue. This sounds reasonable to me, I see that this is supported by the etcd client as well so we can just add this as store.Config options and use it on etcd New. And this will maintain backward compat for 2.0 (if you try to use username and password in this case it will just error out).

The only thing is that I'm not sure this is supported by etcd APIv3, as it uses gRPC for conns I don't see any field supporting username and password but just a plain TLS Config. The client is still in preview but I wanted to initiate the switch slowly as it provides with tons of enhancements. Will look into it. In the meantime I'm not against including this method of auth using the current client, this makes sense to me.

from libkv.

Hi @abronan, thanks for your comment!
Regarding the backward compatibility: I was just concerned about people using the 2.0 client library which does not yet have those attribute in their Config struct. However, most people have probably upgraded until now, what do you think?

from libkv.