You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the introduction of mulit-tenancy, some environment variables will have to be come tenanted. To represent the tenancy of these variables, the tenantSettings table will hold them. The unique id of rows on this table will not be generated, but will instead be a concatenation of the tenantId it is for and the name of the value it represents. For example:
// tenant id is colon-separated from the key of the variable the row represents
id: "1234-1234-1234:ExchangeRatesUrl"
The tenant settings table schema should look like this:
With the introduction of mulit-tenancy, some environment variables will have to be come tenanted. To represent the tenancy of these variables, the
tenantSettings
table will hold them. The unique id of rows on this table will not be generated, but will instead be a concatenation of thetenantId
it is for and the name of the value it represents. For example:The tenant settings table schema should look like this:
tenantSettings
tablemodel.ts
file fortenantSettings
tablePrerequisites
backend
tenants table #3103The text was updated successfully, but these errors were encountered: