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
Multi-Tenancy is based on a mapping of tenant ids to api secrets and endpoints. It should also maintain rows for some basic out-of-band identifying information.
This table should exist on a separate schema from the one that currently exists in the backend package.
Would it make sense to have this table under the public/default schema, and all of the tenanted-resource tables under a "tenant" schema?
Just to keep the conversation up to date, this comment reflects a design that is no longer in scope for this issue. There are no longer separate schemas in scope for this issue.
Multi-Tenancy is based on a mapping of tenant ids to api secrets and endpoints. It should also maintain rows for some basic out-of-band identifying information.
The schema for the tenants table is as follows:
backend
tenant tablemodel.ts
file for tenant tableThe text was updated successfully, but these errors were encountered: