From cbf7db1e84b3d9453a8b2d843b4abedb429ffc87 Mon Sep 17 00:00:00 2001 From: Peter Amiri Date: Thu, 15 Oct 2026 10:35:34 -0700 Subject: [PATCH] docs(cli): correct the deploy e2e fixture README's Keys paragraph The paragraph said the e2e keys were copied verbatim from the sshd/ fixture. sshd/ no longer has an authorized_keys, and the e2e keypair is its own. Describe what the fixture actually holds: its own test keypair, an authorized_keys that is a byte-identical copy of test_key.pub (bind-mounted by docker-compose.yml), and why it is not shared. Co-Authored-By: Claude Opus 5.5 Signed-off-by: Peter Amiri --- cli/lucli/tests/_fixtures/deploy/e2e/README.md | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/cli/lucli/tests/_fixtures/deploy/e2e/README.md b/cli/lucli/tests/_fixtures/deploy/e2e/README.md index 213314bbc8..b244c59e66 100644 --- a/cli/lucli/tests/_fixtures/deploy/e2e/README.md +++ b/cli/lucli/tests/_fixtures/deploy/e2e/README.md @@ -49,10 +49,13 @@ The spec's `beforeAll`/`afterAll` calls these via `DeployShellHelper`. ## Keys -`test_key` / `test_key.pub` / `authorized_keys` are copied verbatim from -the sibling `sshd/` fixture — a deterministic ed25519 keypair with NO -production value. Duplicating them keeps `DeployShellHelper`'s path -conventions happy without cross-fixture coupling. +`test_key` is this fixture's own deterministic ed25519 private key and +`test_key.pub` its public key; `authorized_keys` is a byte-identical +copy of `test_key.pub`, bind-mounted into the container by +`docker-compose.yml`. The keypair has NO production value. It lives +here rather than being shared with the sibling `sshd/` fixture, so the +fixtures stay independent and the `DeployShellHelper`-driven specs find +it at the conventional `/test_key`. ## Phase 3 future work