Forge webhook intake is configured only in config.toml, beside the capture sources #1633

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

Forge webhook intake (forge.intake=webhook, webhook_secret, webhook_addr) runs its own receiver on its own port and is set only by editing config.toml on the server, which breaks the rule that settings are edited through the control plane. Capture sources already give a per-source URL, secret and X-Hub-Signature-256 check in the dashboard. Done when a GitHub repo webhook pointed at a capture source can drive issue/PR work and the separate forge receiver and its config fields are deleted.


Imported from beads archie-core-vqci · GitHub #1507 · type task · priority P2 · created 2026-10-05

Forge webhook intake (forge.intake=webhook, webhook_secret, webhook_addr) runs its own receiver on its own port and is set only by editing config.toml on the server, which breaks the rule that settings are edited through the control plane. Capture sources already give a per-source URL, secret and X-Hub-Signature-256 check in the dashboard. Done when a GitHub repo webhook pointed at a capture source can drive issue/PR work and the separate forge receiver and its config fields are deleted. --- _Imported from beads `archie-core-vqci` · GitHub #1507 · type task · priority P2 · created 2026-10-05_
sam added the mediumtask labels 2026-10-27 13:41:10 +00:00
sam self-assigned this 2026-10-27 13:41:10 +00:00
sam closed this issue 2026-11-08 22:08:49 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#1633