Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Multi-Tenant] backend tenants table #3103

Closed
2 tasks done
Tracked by #2893
njlie opened this issue Nov 18, 2024 · 2 comments · Fixed by #3132
Closed
2 tasks done
Tracked by #2893

[Multi-Tenant] backend tenants table #3103

njlie opened this issue Nov 18, 2024 · 2 comments · Fixed by #3132
Assignees
Labels
pkg: backend Changes in the backend package.

Comments

@njlie
Copy link
Contributor

njlie commented Nov 18, 2024

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:

tenants {
  id: uuid
  email: string
  publicName: string
  apiSecret: string
}
  • Create migration for backend tenant table
  • Create model.ts file for tenant table
@njlie njlie added this to Rafiki Nov 18, 2024
@github-project-automation github-project-automation bot moved this to Backlog in Rafiki Nov 18, 2024
@njlie njlie added the pkg: backend Changes in the backend package. label Nov 18, 2024
@njlie njlie mentioned this issue Nov 18, 2024
38 tasks
@njlie njlie changed the title Operator-Level Tenants Table [Multi-Tenant] Operator-Level Tenants Table Nov 18, 2024
@mkurapov

This comment was marked as outdated.

@njlie njlie changed the title [Multi-Tenant] Operator-Level Tenants Table [Multi-Tenant] backend Tenants Table Nov 20, 2024
@njlie njlie changed the title [Multi-Tenant] backend Tenants Table [Multi-Tenant] backend tenants table Nov 20, 2024
@njlie njlie moved this from Backlog to Todo in Rafiki Nov 25, 2024
@njlie
Copy link
Contributor Author

njlie commented Nov 25, 2024

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.

@njlie njlie self-assigned this Nov 25, 2024
@njlie njlie linked a pull request Nov 25, 2024 that will close this issue
6 tasks
@njlie njlie moved this from Todo to Ready for Review in Rafiki Nov 25, 2024
@golobitch golobitch moved this from Ready for Review to Done in Rafiki Nov 26, 2024
@mkurapov mkurapov closed this as completed Dec 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pkg: backend Changes in the backend package.
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants