etcd/dev-guide at 15d6a11e14c5cf36770f9b3506ed9bc7a2318eb1 - etcd

mirror of https://github.com/etcd-io/etcd.git synced 2024-09-27 06:25:44 +00:00

History

Piotr Tabor 6c0e4d97f1 Introduce grpc-1.30+ compatible client/v3/naming API.

This is not yet implementation, just API and tests to be filled
with implementation in next CLs,
tracked by: https://github.com/etcd-io/etcd/issues/12652

We propose here 3 packages:
 - clientv3/naming/endpoints ->
    That is abstraction layer over etcd that allows to write, read &
    watch Endpoints information. It's independent from GRPC API. It hides
    the storage details.

 - clientv3/naming/endpoints/internal ->
    That contains the grpc's compatible Update class to preserve the
    internal JSON mashalling format.

 - clientv3/naming/resolver ->
   That implements the GRPC resolver API, such that etcd can be
   used for connection.Dial in grpc.

Please see the grpc_naming.md document changes & grpcproxy/cluster.go
new integration, to see how the new abstractions work.

Signed-off-by: Chao Chen <chaochn@amazon.com>

2023-10-19 12:59:24 -07:00

apispec/swagger

etcdserver: do not allow creating empty role

2019-07-24 17:41:24 -04:00

api_concurrency_reference_v3.md

*: revert module import paths

2019-05-28 15:39:35 -07:00

api_grpc_gateway.md

documentation: initial metadata additions for website generation (#10596 )

2019-04-01 13:57:24 -07:00

api_reference_v3.md

etcdserver: do not allow creating empty role