-
Notifications
You must be signed in to change notification settings - Fork 4.1k
settings: redefine TenantReadOnly to take its value from the system tenant #85729
Copy link
Copy link
Closed
Closed
Copy link
Labels
A-configurabilityPertains to cluster settings, CLI flags, env vars etcPertains to cluster settings, CLI flags, env vars etcC-enhancementSolution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)T-shared-systemsShared Systems TeamShared Systems Team
Description
As discussed with @stevendanna @dt and @ajwerner :
- we want a setting class which uses a single shared value between system and secondary tenants.
- the current behavior of TenantReadOnly (one value per tenant) can be readily emulated by a TenantReadWrite setting + an OVERRIDE in the system tenant.
So to achieve point 1, we can redefine TenantReadOnly to make settings take their value from the system tenant.
Informs #77472
Epic: CRDB-6671
Jira issue: CRDB-18406
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
A-configurabilityPertains to cluster settings, CLI flags, env vars etcPertains to cluster settings, CLI flags, env vars etcC-enhancementSolution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)T-shared-systemsShared Systems TeamShared Systems Team