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.
22 lines
606 B
Python
22 lines
606 B
Python
"""Plattform-Modul: Admin-Zugang und Quota-Bypass (083)."""
|
|
from rights_registry import CapabilityRegistration, register_capability
|
|
|
|
register_capability(
|
|
CapabilityRegistration(
|
|
id="platform.admin.access",
|
|
name="Plattform-Admin-Bereich",
|
|
domain="platform",
|
|
module="platform",
|
|
min_account_state="platform_admin",
|
|
)
|
|
)
|
|
register_capability(
|
|
CapabilityRegistration(
|
|
id="platform.club_quota.bypass",
|
|
name="Vereins-Kontingent-Bypass",
|
|
domain="quota_bypass",
|
|
module="platform",
|
|
min_account_state="platform_admin",
|
|
)
|
|
)
|