Feature: Tenant-Specific Configuration Infrastructure #24

New issue

Closed

opened 2026-07-05 20:20:11 +00:00 by psycodepath · 0 comments

psycodepath commented

2026-07-05 20:20:11 +00:00

Owner

Motivation

To support different authentication strategies (like LDAP, Authelia, or local) and other settings per tenant, we need a database-backed configuration store that is scoped to each isolated tenant SQLite database.

Description

Create the schema and repository to read/write system configuration values dynamically from the tenant's sqlite database.

User Story

As a system administrator, I want to configure tenant-specific settings inside each tenant's isolated database so that I don't leak configurations between tenants and can configure them independently.

Gherkin Feature

Feature: Tenant-Specific Configuration
  As an administrator
  I want to save settings for a tenant
  So that they only apply to that specific tenant's database context

  Scenario: Read tenant-specific config
    Given I have a tenant database for "family1"
    And "family1" database contains setting "auth_strategy" as "ldap"
    When the system requests "auth_strategy" for "family1"
    Then the value "ldap" is returned

Acceptance Criteria

Database migration to create a system_settings or auth_config table in tenant databases.
Implementation of TenantAuthSettingsRepository in Infrastructure.
Unit tests verifying that configuration values are retrieved from the correct tenant database.

### Motivation To support different authentication strategies (like LDAP, Authelia, or local) and other settings per tenant, we need a database-backed configuration store that is scoped to each isolated tenant SQLite database. ### Description Create the schema and repository to read/write system configuration values dynamically from the tenant's sqlite database. ### User Story As a system administrator, I want to configure tenant-specific settings inside each tenant's isolated database so that I don't leak configurations between tenants and can configure them independently. ### Gherkin Feature ```gherkin Feature: Tenant-Specific Configuration As an administrator I want to save settings for a tenant So that they only apply to that specific tenant's database context Scenario: Read tenant-specific config Given I have a tenant database for "family1" And "family1" database contains setting "auth_strategy" as "ldap" When the system requests "auth_strategy" for "family1" Then the value "ldap" is returned ``` ### Acceptance Criteria - [ ] Database migration to create a `system_settings` or `auth_config` table in tenant databases. - [ ] Implementation of `TenantAuthSettingsRepository` in Infrastructure. - [ ] Unit tests verifying that configuration values are retrieved from the correct tenant database.

psycodepath referenced this issue from a commit

2026-07-05 20:21:54 +00:00

feat: implement tenant-specific configuration infrastructure (#24)

psycodepath referenced this issue from a pull request that will close it,

2026-07-05 20:21:55 +00:00

feat: implement tenant-specific configuration infrastructure (#24) #26

psycodepath closed this issue

2026-07-05 20:23:20 +00:00

psycodepath referenced this issue from a commit

2026-07-05 20:23:21 +00:00

Merge pull request 'feat: implement tenant-specific configuration infrastructure (#24)' (#26) from feature/tenant-specific-config into main