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

A rule can be written against a capability no configured provider delivers #116

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

What a person cannot do today

Tell, while writing a rule, whether the capability being chosen can be delivered. The picker lists every resource key the deployment knows, including keys owned by an integration that is not configured; the wiki-site key exists in a fresh database before the wiki integration has been set up at all. The rule is written, the set is attached to a product, and the product's readiness section is where the unmet provider finally appears.

What they should be able to do

See at the point of choice that a key belongs to a provider that is not configured, and choose it deliberately.

Why it matters

This is one of the two ways a product ends up unable to deliver, the other being a provider that loses its configuration later, and it is the avoidable one: the fact is known when the picker is drawn.

Where

The rule form's resource-key picker and the provider registry it can ask.

Done when

A key owned by an unconfigured provider is marked as such in the picker, naming the provider, and choosing one still works.

Migrated from status/issues.md at b7a0e15

## What a person cannot do today Tell, while writing a rule, whether the capability being chosen can be delivered. The picker lists every resource key the deployment knows, including keys owned by an integration that is not configured; the wiki-site key exists in a fresh database before the wiki integration has been set up at all. The rule is written, the set is attached to a product, and the product's readiness section is where the unmet provider finally appears. ## What they should be able to do See at the point of choice that a key belongs to a provider that is not configured, and choose it deliberately. ## Why it matters This is one of the two ways a product ends up unable to deliver, the other being a provider that loses its configuration later, and it is the avoidable one: the fact is known when the picker is drawn. ## Where The rule form's resource-key picker and the provider registry it can ask. ## Done when A key owned by an unconfigured provider is marked as such in the picker, naming the provider, and choosing one still works. Migrated from status/issues.md at b7a0e15
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/entitlements area/integrations area/operator-ui
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#116