Skip to content
This repository has been archived by the owner on Apr 15, 2018. It is now read-only.

Support for etcd 3 #124

Open
hseeberger opened this issue Sep 29, 2016 · 5 comments
Open

Support for etcd 3 #124

hseeberger opened this issue Sep 29, 2016 · 5 comments

Comments

@hseeberger
Copy link
Owner

No description provided.

@Chumper
Copy link

Chumper commented Jan 16, 2017

etcd3 should be straitght forward to implement. I used the grpc api on my own adapter: https://github.com/Chumper/etcd3-scala
It is far from perfect, I use it to learn scala along the way but I hope you can use it as inspiration for an etcd3 version.

I can also try to create an etcd3 version as plugin if you want.

@hseeberger
Copy link
Owner Author

Thanks, but I'm already on it, thereby changing some semantics of ConstructR ;-)

@Chumper
Copy link

Chumper commented Jan 17, 2017

Yeah, afterwards I saw your etcd3 branch that you recently started. Good work btw.

@yi719
Copy link

yi719 commented Sep 12, 2017

Hi, are there any plans on releasing Support for etcd 3 ?

@lutzh
Copy link

lutzh commented Sep 19, 2017

I set up a little test system with constructr and unaware of etcd3 support being w.i.p., I naively used etcd3. And as far as I can tell it's working just fine !?!

Is my understanding correct, that the etcd3 support means making use of the gRPC interface of etcd3, but even without, constructr 0.17 works fine with etcd3 (because of etcd3's Json backwards compatibility)? From https://coreos.com/etcd/docs/latest/op-guide/v2-migration.html:
The data store v2 is still accessible from the API v2 after upgrading to etcd3. Thus, it will work as before and require no application changes.

What problems should I expect when using constructr 0.17 with etcd3?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants