issues — bigbes/tarantool-etcd

id	content_hash	title	description	notes	status	priority	issue_type	assignee	estimated_minutes	created_at	created_by	owner	updated_at	closed_at	external_ref	compacted_at	compacted_at_commit	original_size	metadata	last_activity	due_at	defer_until	started_at
tarantool-etcd-zkg	72a34c0ab42f90eede7cbbfd3ec5f7ef4f98cdbb5232099ad2926aaa87a61111	Learner: conformance — join real etcd cluster, assert log replication	End-to-end test in tests/conformance: SpawnEtcd (or a small etcd cluster), MemberAddAsLearner the tarantool node with its advertise_peer_url, wait for it to become a healthy learner, then: (1) Put on the real etcd leader, assert it appears via Range on the tarantool learner with the SAME mod_revision; (2) assert MemberList on the cluster shows the tarantool node as IsLearner=true; (3) lease grant + key-with-lease on the leader replicates and the learner reflects lease attachment; (4) auth enable on the leader propagates; (5) force a snapshot (lower --snapshot-count, churn keys past compaction) and assert the learner recovers via snapshot receive. Use the harness, never tt start (memory feedback_use_harness_not_tt).	This is the correctness oracle for the whole epic — each phase above is unverifiable in isolation against real etcd without it. Gate behind a build tag / env since it boots a foreign etcd cluster.	open	2	task	NULL	NULL	2026-05-20T06:45:18Z	Eugene Blikh	bigbes@gmail.com	2026-05-20T06:45:18Z	NULL	NULL	NULL	NULL	NULL	<binary>	NULL	NULL	NULL	NULL
tarantool-etcd-zwg	5f1f8ad7dadfa6be0ecaa0dc1d71f690076e930bc5073feb538b71faf1f2d7d6	iproto-verify: etcd_user_get vs Auth.UserGet	Add Lua testkit verification for etcd_user_get (mirrors gRPC Auth.UserGet). Successful path: assert response shape matches the gRPC response message after MsgPack round-trip. Error path: at least one error case asserting {code, message} matches app/etcd/errors.lua catalog. Exercise at least one non-default option if applicable. Goes in test/iproto_parity_test.lua under group iproto/parity/auth. Call shape: local resp = etcd_user_get(req).	Verification-only. Wrapper exists at app/etcd/api.lua. Epic tarantool-etcd-w8q.	open	3	task	NULL	NULL	2026-05-19T14:54:08Z	Eugene Blikh	bigbes@gmail.com	2026-05-19T14:54:08Z	NULL	NULL	NULL	NULL	NULL	<binary>	NULL	NULL	NULL	NULL
tarantool-etcd-zws	b99aec7b0025f26f4e59b5bf3e6287ee00f117d8f119775c13dcfbb23132d00e	Replica route: revision alignment with upstream	In replica mode the local global revision sequence (box.sequence in revision.lua) must mirror upstream's revisions exactly so that Range/Watch reads return etcd-consistent create_revision/mod_revision/header.revision. Work: - While replica mode is active, the local revision allocator must NOT mint its own revisions for replicated writes; it must set revision = the upstream mod_revision carried by each Range/Watch event. - Decide handling of the box.sequence: drive it to upstream's current revision (set, not next()) as events apply, or bypass it entirely for replicated mutations via the *_internal write paths. - Ensure header.revision returned to local clients equals the latest synced upstream revision, and compact_revision tracks upstream compaction. This is cross-cutting with bootstrap + watch-tail; it defines the invariant both must uphold.	revision.lua owns the box.sequence. Replicated writes likely go through put_internal/delete_range_internal with an explicit revision arg to avoid double-allocation.	open	2	task	NULL	NULL	2026-05-20T06:17:55Z	Eugene Blikh	bigbes@gmail.com	2026-05-20T06:17:55Z	NULL	NULL	NULL	NULL	NULL	<binary>	NULL	NULL	NULL	NULL

~bigbes/tarantool-etcd · issues