[UX] Add pattern-aware selectors for connector policy references #39

New Issue

zemion · 2026-07-29T02:29:32+02:00

zemion commented

2026-07-29 02:29:32 +02:00

Problem

Files connector policy currently uses multiline raw values for allowed/denied connection IDs, credential IDs, and providers. These fields accept wildcard patterns, so a plain dropdown would lose existing semantics.

Work

Provide discoverable multi-select choices for known connections, credentials, and providers.
Preserve explicit wildcard/custom patterns as first-class chips or rows.
Distinguish exact references from patterns and show unresolved references without dropping them.
Explain inherited policy provenance and conflicts between allow/deny entries.
Keep path and URL pattern editors as pattern inputs unless a dedicated path/endpoint browser is available.

Acceptance criteria

Administrators can choose known resources without copying IDs and can still author, inspect, and round-trip wildcard policy rules.

Parent: GovOPlaN/govoplan-core#272

## Problem Files connector policy currently uses multiline raw values for allowed/denied connection IDs, credential IDs, and providers. These fields accept wildcard patterns, so a plain dropdown would lose existing semantics. ## Work - Provide discoverable multi-select choices for known connections, credentials, and providers. - Preserve explicit wildcard/custom patterns as first-class chips or rows. - Distinguish exact references from patterns and show unresolved references without dropping them. - Explain inherited policy provenance and conflicts between allow/deny entries. - Keep path and URL pattern editors as pattern inputs unless a dedicated path/endpoint browser is available. ## Acceptance criteria Administrators can choose known resources without copying IDs and can still author, inspect, and round-trip wildcard policy rules. Parent: https://git.add-ideas.de/GovOPlaN/govoplan-core/issues/272

zemion added the