Dashboard UI for playbook bindings #476

Closed
opened 2026-10-27 13:36:28 +00:00 by sam · 0 comments
Owner

The t2db.4 backend shipped the CRUD API (POST/GET/PATCH/DELETE /api/bindings + POST /api/bindings/{id}/approve) plus the state machine and HMAC wiring. Operators cannot author bindings from the dashboard yet: a list-and-approve page exists in api_binding.go's response shape but the matching ui/src/ feature folder does not. Build the click-through editor mirroring ui/src/mappings/ -- the actual convention there is .jsx, not .js (mapping-editor.jsx, mappings.jsx, mappings.css) -- follow that file extension, not payload-field-mapping.md:145-152's literal naming if it says .js. Components: source matcher, mapping picker, workflow picker, secret input, owner/repo pin input, state-machine controls (create -> edit -> approve -> armed). See docs/prds/webhook-intake-security.md and docs/prds/payload-field-mapping.md.

RESOLVED 2026-09-03 (commit ac42f64): the backend multi-repo correctness gap is fixed. binding.Binding now has optional Owner/Repo fields (Validate rejects setting only one); resolveBindingRepo (internal/daemon/daemon.go) dispatches to a pinned binding's own owner/repo unconditionally, falling back to the existing single-configured-repo behavior when unpinned. Wired through the API request/response shape already. Remaining scope for this ticket is UI-only: the dashboard editor itself, including an owner/repo input field for the pin added above.

Acceptance criteria

The click-through editor exists in ui/src/bindings/ (or the confirmed correct convention), covering create -> edit -> approve -> armed, including an owner/repo pin input. Backend correctness (multi-repo dispatch) is already resolved -- not part of this ticket's remaining acceptance.

Close reason

Backend Owner/Repo fix (ac42f64) + full dashboard UI (85761c4, mirroring ui/src/mappings/) both landed. Full state machine (draft->edit->pending_approval->approve->armed->delete) verified end-to-end in a real browser. Also fixed a related bug found in the process (empty-secret-on-edit rejected, commit 51ca509).


Imported from beads archie-core-t2db.8 · GitHub #687 · type feature · priority P2 · created 2026-09-02 · closed 2026-09-02

The t2db.4 backend shipped the CRUD API (POST/GET/PATCH/DELETE /api/bindings + POST /api/bindings/{id}/approve) plus the state machine and HMAC wiring. Operators cannot author bindings from the dashboard yet: a list-and-approve page exists in api_binding.go's response shape but the matching ui/src/ feature folder does not. Build the click-through editor mirroring ui/src/mappings/ -- the actual convention there is .jsx, not .js (mapping-editor.jsx, mappings.jsx, mappings.css) -- follow that file extension, not payload-field-mapping.md:145-152's literal naming if it says .js. Components: source matcher, mapping picker, workflow picker, secret input, owner/repo pin input, state-machine controls (create -> edit -> approve -> armed). See docs/prds/webhook-intake-security.md and docs/prds/payload-field-mapping.md. RESOLVED 2026-09-03 (commit ac42f64): the backend multi-repo correctness gap is fixed. binding.Binding now has optional Owner/Repo fields (Validate rejects setting only one); resolveBindingRepo (internal/daemon/daemon.go) dispatches to a pinned binding's own owner/repo unconditionally, falling back to the existing single-configured-repo behavior when unpinned. Wired through the API request/response shape already. Remaining scope for this ticket is UI-only: the dashboard editor itself, including an owner/repo input field for the pin added above. ### Acceptance criteria The click-through editor exists in ui/src/bindings/ (or the confirmed correct convention), covering create -> edit -> approve -> armed, including an owner/repo pin input. Backend correctness (multi-repo dispatch) is already resolved -- not part of this ticket's remaining acceptance. ### Close reason Backend Owner/Repo fix (ac42f64) + full dashboard UI (85761c4, mirroring ui/src/mappings/) both landed. Full state machine (draft->edit->pending_approval->approve->armed->delete) verified end-to-end in a real browser. Also fixed a related bug found in the process (empty-secret-on-edit rejected, commit 51ca509). --- _Imported from beads `archie-core-t2db.8` · GitHub #687 · type feature · priority P2 · created 2026-09-02 · closed 2026-09-02_
sam added the mediumfeature labels 2026-10-27 13:36:28 +00:00
sam self-assigned this 2026-10-27 13:36:28 +00:00
sam closed this issue 2026-10-27 13:36:28 +00:00
sam added a new dependency 2026-10-27 13:42:06 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Reference: sam/archie#476