feat(modules): settings_overrides and module_state database migration #94

Closed
opened 2026-02-14 19:45:34 +00:00 by forbes · 0 comments
Owner

Ref: docs/MODULES.md §5.2, §11 step 1

Create migration for the module system's persistence layer.

settings_overrides table:

  • key (TEXT PK) — dotted path like auth.ldap.enabled
  • value (JSONB) — typed value
  • updated_by (TEXT) — username
  • updated_at (TIMESTAMPTZ)

module_state table:

  • module_id (TEXT PK) — auth, projects, audit, etc.
  • enabled (BOOLEAN)
  • updated_by (TEXT)
  • updated_at (TIMESTAMPTZ)

Update testutil.TruncateAll to include new tables.

**Ref:** docs/MODULES.md §5.2, §11 step 1 Create migration for the module system's persistence layer. **`settings_overrides` table:** - `key` (TEXT PK) — dotted path like `auth.ldap.enabled` - `value` (JSONB) — typed value - `updated_by` (TEXT) — username - `updated_at` (TIMESTAMPTZ) **`module_state` table:** - `module_id` (TEXT PK) — `auth`, `projects`, `audit`, etc. - `enabled` (BOOLEAN) - `updated_by` (TEXT) - `updated_at` (TIMESTAMPTZ) Update `testutil.TruncateAll` to include new tables.
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: kindred/silo#94