Skip to content

docs(design): promote admin dashboard from proposed to partial #675

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
bootjp merged 3 commits into from
Apr 26, 2026
Merged

docs(design): promote admin dashboard from proposed to partial #675

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
1a5b65f
docs(design): promote admin dashboard from proposed to partial
bootjp Apr 26, 2026
7617daf
docs(design): correct P1/P2 status in admin dashboard partial doc
bootjp Apr 26, 2026
25ee3dc
docs(design): align header prose with P2 partial status table
bootjp Apr 26, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 19 additions & 1 deletion ...gn/2026_04_24_proposed_admin_dashboard.md → ...ign/2026_04_24_partial_admin_dashboard.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,8 +1,26 @@
# elastickv Admin Dashboard Design

**Status:** Proposed
**Status:** Partial — P1 and P3 have shipped in full; P2 has shipped its read-only slice with the write path still in flight; P4 has shipped TLS / role / CSRF and lands its operator documentation alongside this rename. See the status table below for the per-phase breakdown.
**Author:** bootjp
**Date:** 2026-04-24
**Last updated:** 2026-04-26 (renamed from `_proposed_` to `_partial_` after P1, P3, and the read-only slice of P2 landed)

## Implementation status (as of 2026-04-26)

| Phase | Status | Landed via |
|---|---|---|
| **P1** — `internal/admin/` skeleton, auth, DynamoDB list/create/describe/delete, AdminForward (Section 3.3 acceptance criteria 1–4 + 6; criterion 5 deferred — see outstanding items) | ✅ shipped | #634, #635, #644, #648 |
| **P2** — S3 bucket list/create/delete/ACL, DescribeTable | 🟡 partial — read-only slice 1 landed in #658; write paths (slice 2a, #669) and AdminForward integration (slice 2b, #673) are still in flight |
| **P3** — React SPA + embed | ✅ shipped | #649, #650 |
| **P4** — TLS, read-only role, CSRF, `docs/admin.md` | 🟡 mostly shipped — TLS / role / CSRF are live in P1, operator doc in #674 |

Outstanding open items (kept here so future readers know what is still owed against the original proposal):

- **AdminForward acceptance criterion 5** — rolling-upgrade compatibility flag (`admin.leader_forward_v2`). Deferred behind a cluster-version bump; not blocking dashboard usability today because every node forwards through the same `pb.AdminOperation` enum.
- **S3 object browser** — explicitly called out as "next phase" in Section 2 Non-goals; no work item yet.
- **Operator-visible TLS cert reload** — out of scope; restart-to-rotate is the documented model in `docs/admin.md`.

When the rolling-upgrade flag lands, this doc is renamed `2026_04_24_implemented_admin_dashboard.md` per `docs/design/README.md`'s lifecycle convention.

---

Expand Down
Loading