Skip to content

docs/design: rename admin purge queue proposal → implemented (Phase 6) #800

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

Open
bootjp wants to merge 1 commit into
base: main
Choose a base branch
from
+17 −1
Open

docs/design: rename admin purge queue proposal → implemented (Phase 6) #800

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
18 changes: 17 additions & 1 deletion .../2026_05_16_proposed_admin_purge_queue.md → ...26_05_16_implemented_admin_purge_queue.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,9 +1,25 @@
# Admin Queue Peek and Purge (DLQ-Aware) for the SQS Web Console

**Status:** Proposed
**Status:** Implemented
**Author:** bootjp
**Date:** 2026-05-16

## Implementation history

| Phase | PR | Landed |
|-------|-----|--------|
| 1 (this doc, proposal) | #757 | 2026-05-16 |
| 2 (`AdminPurgeQueue` + `IsDLQ`/`DLQSources`) | #771 | 2026-05-17 |
| 3 (`AdminPeekQueue` backend) | #794 | 2026-05-20 |
| 4 (HTTP handler + bridge) | #797 | 2026-05-21 |
| 5 (SPA Messages tab + Purge button + DLQ chips) | #798 | 2026-05-21 |

Out-of-scope follow-ups (tracked separately, not gating this rename):
- Throttle integration (`bucketActionAdminPeek` + dedicated per-queue admin-peek bucket per §3.1)
- Audit logging + Prometheus counters per §3.6
- `principalForReadSensitive` live `RoleStore` re-check (Goal 8, blocked on wider RoleStore plumbing)
- Page-size selector (20 / 50 / 100) + response-size warning
Comment on lines +17 to +21
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot May 22, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The 'Out-of-scope follow-ups' list identifies several features as deferred (Throttle integration, Audit/Prometheus, live RoleStore re-check, and Page-size selector). However, the body of this document (e.g., §3.1, §3.6, Goal 8 in §2.1, and §3.5) still describes these features as if they were implemented. Since this document is being marked as 'Implemented' and features like 'Throttle integration' are significant for managing operational risk, please update the document to reflect these deferrals and detail any mitigation strategies used in their absence to align with repository guidelines.

References
  1. When a design document identifies a significant operational risk, such as the inability to perform rolling upgrades, it must also detail potential mitigation strategies, like implementing a temporary "bridge" or "proxy" mode.


---

## 1. Background and Motivation
Expand Down
Loading