Lars
4130a63dfe
All checks were successful
Deploy Development / deploy (push) Successful in 44s
Test Suite / pytest-backend (push) Successful in 42s
Test Suite / lint-backend (push) Successful in 0s
Test Suite / build-frontend (push) Successful in 13s
Test Suite / k6 /health Baseline (push) Successful in 35s
Test Suite / playwright-tests (push) Successful in 1m51s
- Updated the capability catalog to reflect a registry-first approach, requiring modules to register rights and quotas upon implementation. - Enhanced the backend to synchronize the rights registry with the database, ensuring only registered capabilities and features are displayed in the admin matrix. - Modified SQL queries in the admin rights router to filter capabilities and features based on module registration. - Updated documentation to clarify the new rights and features registry process, replacing the previous catalog-first method. - Incremented application version to 0.8.201 and updated database schema version to 20260606084 to reflect these changes.
16 lines
608 B
SQL
16 lines
608 B
SQL
-- Migration 084: Modul-Registrierung für Rechte & Kontingente (Registry-first)
|
|
-- capabilities/features mit module=NULL = Legacy-Katalog-Seed (nicht in Admin-Matrix).
|
|
-- module IS NOT NULL = vom Modul bei Implementierung registriert.
|
|
|
|
ALTER TABLE capabilities
|
|
ADD COLUMN IF NOT EXISTS module TEXT;
|
|
|
|
ALTER TABLE features
|
|
ADD COLUMN IF NOT EXISTS module TEXT;
|
|
|
|
CREATE INDEX IF NOT EXISTS idx_capabilities_module
|
|
ON capabilities(module) WHERE module IS NOT NULL AND active = true;
|
|
|
|
CREATE INDEX IF NOT EXISTS idx_features_module
|
|
ON features(module) WHERE module IS NOT NULL AND active = true;
|