An external system cannot be told when something changes in the console #77
Open
opened 2026-09-21 07:18:23 +00:00 by cgalo5758
·
1 comment
Labels
Clear labels
accessibility
area/billing
area/catalog
area/discourse
area/domains
area/entitlements
area/fedwiki
area/identity
area/integrations
area/licensing
area/member-ui
area/meta
area/operator-ui
area/ops
area/testing
duplicate
good-first-issue
invalid
privacy
security
upstream
wontfix
A barrier for people using assistive technology or a keyboard alone.
The Stripe mirror, checkout, subscriptions, invoices, fulfillment.
Products, prices, plan ladders, purchasability.
The Discourse integration.
The domains registry, claims, placements, the certificate ask.
Entitlement sets, rules, grants, pools, provisioning.
The Federated Wiki integration and farm sync.
Sign-in, sessions, persons, organizations, workspaces, roles.
The provider registry, outbox and webhooks in general.
Licenses, the contributor agreement, SPDX headers.
Member pages.
The repository itself, its contributing guide, CI, the tracker and the workflow.
Operator pages, forms, lists, the design system.
Deployment, configuration, migrations, workflows, instance settings.
The test stack, screens, lint, walkthroughs.
Closed because another issue already covers it.
Small, self-contained, and explained enough to be a first contribution.
Closed because it is not a ticket for this repository.
Touches what a person's data reveals.
Touches authentication, authorization, secrets or data exposure.
Waits on another repository or project before it can move.
Closed because it will not be done, with the reason in the last comment.
kind
bug
The software does something other than what it promises; closed when it again does what it promises.
kind
debt
Code, tests or tooling to clean up with nothing visible changing; closed when they are cleaner.
kind
design
A question to settle before work can be defined; closed when the decision is written down.
kind
docs
Documentation that is wrong or missing; closed when it says the right thing.
kind
enhancement
Something the software does not do yet; closed when it does.
priority
critical
Blocks the active milestone or harms members now.
priority
high
Next in line inside the active milestone.
priority
low
Inside the active milestone, when nothing else is left.
priority
medium
Inside the active milestone, after the high ones.
Milestone
No items
No Milestone
Projects
Clear projects
No projects
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: wiki-cafe/member-console#77
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
What a person cannot do today
Have another system react to events in the console. Integrations that ship inside the console receive events through the registry, but a system outside it has nothing to subscribe to.
What they should be able to do
Register a webhook endpoint for a set of event types, receive signed deliveries with retries, and see the delivery log.
Why it matters
Deployments run other software beside the console, and the console is where membership changes first; without outbound events every other system polls or drifts.
Where
The integration outbox and webhook-event tables, a delivery worker, an operator page for endpoints and their deliveries.
Done when
An operator can register an endpoint, events are delivered with a signature and retried on failure, and each delivery is visible with its outcome.
23d5badsupplies half of this. Every change that alters what an application should hold (a pool's entitlements, an organization's membership, ownership or status, a person cut off everywhere) now writes an outbox row in the same transaction, through database triggers, and a relay recomputes the affected desired-state records: one per connection and recipient, with a generation that rises when the content changes.The other half is still missing: a transport that delivers those records to a system outside the console, signed and retried, and a page that shows each delivery. That arrives with the published integration contract, which pushes over HTTP with signatures in both directions. The shape differs from the one asked for here: the console delivers the whole state a recipient should have, not a stream of individual events, so a receiver that misses one delivery is corrected by the next.
Design: https://git.coopcloud.tech/wiki-cafe/member-console/src/commit/23d5bad/openspec/changes/archive/2026-10-06-integration-delivery-core/design.md