wiki-cafe/member-console
0
0
Fork 0
Code Issues 140 Pull Requests Packages Projects 1 Releases Activity

A deployment cannot turn off an integration it does not offer #56

New Issue
Open
opened 2026-09-21 07:18:17 +00:00 by cgalo5758 · 0 comments
cgalo5758 commented 2026-09-21 07:18:17 +00:00
Owner
Copy Link
Copy Source

What a person cannot do today

Run the console without an integration that ships with it. Every registered provider appears in the operator panel, contributes its resource keys to the rule pickers and shows as unconfigured on the pages that report readiness, whether or not the deployment intends to offer it.

What they should be able to do

Turn an integration off for the deployment, so its pages, its cards and its resource keys stop appearing and nothing reports it as unfinished work.

Why it matters

A deployment that offers one of the integrations and not the other carries permanent unconfigured rows it can never clear, and an operator cannot tell a provider that is missing configuration from one the deployment does not use.

Where

The provider registry and the deployment settings surface, once it exists.

Done when

An integration can be disabled for the deployment, the surfaces it owns disappear with it, its resource keys leave the pickers, and readiness reporting ignores it.

Migrated from status/issues.md at b7a0e15

## What a person cannot do today Run the console without an integration that ships with it. Every registered provider appears in the operator panel, contributes its resource keys to the rule pickers and shows as unconfigured on the pages that report readiness, whether or not the deployment intends to offer it. ## What they should be able to do Turn an integration off for the deployment, so its pages, its cards and its resource keys stop appearing and nothing reports it as unfinished work. ## Why it matters A deployment that offers one of the integrations and not the other carries permanent unconfigured rows it can never clear, and an operator cannot tell a provider that is missing configuration from one the deployment does not use. ## Where The provider registry and the deployment settings surface, once it exists. ## Done when An integration can be disabled for the deployment, the surfaces it owns disappear with it, its resource keys leave the pickers, and readiness reporting ignores it. Migrated from status/issues.md at b7a0e15
cgalo5758 added the
kind
enhancement
area/integrationsarea/ops labels 2026-09-21 07:18:17 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
accessibility
A barrier for people using assistive technology or a keyboard alone.
 area/billing
The Stripe mirror, checkout, subscriptions, invoices, fulfillment.
 area/catalog
Products, prices, plan ladders, purchasability.
 area/discourse
The Discourse integration.
 area/domains
The domains registry, claims, placements, the certificate ask.
 area/entitlements
Entitlement sets, rules, grants, pools, provisioning.
 area/fedwiki
The Federated Wiki integration and farm sync.
 area/identity
Sign-in, sessions, persons, organizations, workspaces, roles.
 area/integrations
The provider registry, outbox and webhooks in general.
 area/licensing
Licenses, the contributor agreement, SPDX headers.
 area/member-ui
Member pages.
 area/meta
The repository itself, its contributing guide, CI, the tracker and the workflow.
 area/operator-ui
Operator pages, forms, lists, the design system.
 area/ops
Deployment, configuration, migrations, workflows, instance settings.
 area/testing
The test stack, screens, lint, walkthroughs.
 duplicate
Closed because another issue already covers it.
 good-first-issue
Small, self-contained, and explained enough to be a first contribution.
 invalid
Closed because it is not a ticket for this repository.
 privacy
Touches what a person's data reveals.
 security
Touches authentication, authorization, secrets or data exposure.
 upstream
Waits on another repository or project before it can move.
 wontfix
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.
No labels area/integrations area/ops
kind
enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
3wordchant Bortseb (Robert Best) cgalo5758 (Christian Galo) renovate-bot (Comrade Renovate Bot)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: wiki-cafe/member-console#56