docs(e2e): clarify Infisical password retrieval in the runbook (BUNYIP-148) #181

Merged

nrupard merged 1 commit from docs/bunyip-148-e2e-infisical-password into main

2026-06-22 18:07:37 +02:00

nrupard commented

2026-06-22 18:01:09 +02:00

Owner

What

Clarifies the password step of the BUNYIP-148 first-time setup runbook in dev-docs/e2e.md.

Step 2 now points at the real c-01 path: the docker-repo just e2e-bootstrap recipe (DEV-378), which runs the bunyip-e2e-bootstrap binary shipped in the deployed image (BUNYIP-156), instead of the dev-only cargo run in a source-mounted container.
Documents pulling BUNYIP_E2E_TEST_USER_PASSWORD from Infisical: infisical secrets get test_user_password --path=/bunyip/e2e --env=staging --plain.
Corrects a common misread: /bunyip/e2e/test_user_password is an Infisical SECRET PATH (project/env/folder/key inside the secrets manager), NOT a filesystem directory. Its absence on disk is expected.
Notes that bunyip's c-01 secrets currently live in sops and Infisical wiring is a future item, so the value is likely not provisioned yet: it is the shared password the operator chooses, seeds with, and records both at the Infisical path and as the E2E_STAGING_PASSWORD CI secret.

Docs-only. No em-dash.

#BUNYIP-148

## What Clarifies the password step of the BUNYIP-148 first-time setup runbook in `dev-docs/e2e.md`. - Step 2 now points at the real c-01 path: the docker-repo `just e2e-bootstrap` recipe (DEV-378), which runs the `bunyip-e2e-bootstrap` binary shipped in the deployed image (BUNYIP-156), instead of the dev-only `cargo run` in a source-mounted container. - Documents pulling `BUNYIP_E2E_TEST_USER_PASSWORD` from Infisical: `infisical secrets get test_user_password --path=/bunyip/e2e --env=staging --plain`. - Corrects a common misread: `/bunyip/e2e/test_user_password` is an Infisical SECRET PATH (project/env/folder/key inside the secrets manager), NOT a filesystem directory. Its absence on disk is expected. - Notes that bunyip's c-01 secrets currently live in sops and Infisical wiring is a future item, so the value is likely not provisioned yet: it is the shared password the operator chooses, seeds with, and records both at the Infisical path and as the `E2E_STAGING_PASSWORD` CI secret. Docs-only. No em-dash. #BUNYIP-148

nrupard added 1 commit

2026-06-22 18:01:09 +02:00

docs(e2e): clarify the Infisical password retrieval in the runbook

E2E / Playwright against deployment (pull_request) Failing after 32s

Details

Check / fmt + clippy + build + tests (pull_request) Successful in 6m27s

Details

Create release / Create release from merged PR (pull_request) Has been skipped

Details

42cb25d150

Rewrites runbook step 2 to the real c-01 path: run the docker-repo `just e2e-bootstrap` recipe (DEV-378), which runs the bunyip-e2e-bootstrap binary now shipped in the deployed image (BUNYIP-156), instead of the dev-only `cargo run` in a source-mounted container.

Adds the password guidance that was missing: how to pull BUNYIP_E2E_TEST_USER_PASSWORD from Infisical (`infisical secrets get test_user_password --path=/bunyip/e2e --env=staging --plain`), and clears up a common misread - `/bunyip/e2e/test_user_password` is an Infisical SECRET PATH (project/env/folder/key inside the secrets manager), not a filesystem directory, so it being absent on disk is expected. Notes that bunyip's c-01 secrets currently live in sops and Infisical wiring is a future item, so the value is likely not provisioned yet: it is the shared password the operator chooses, seeds with, and records both at the Infisical path and as the E2E_STAGING_PASSWORD CI secret.

#BUNYIP-148

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

nrupard scheduled this pull request to auto merge when all checks succeed

2026-06-22 18:03:21 +02:00