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
Currently, Rafiki can only be used by a single ASE. We want that a single Rafiki instance to be able to handle multiple tenants (ASEs).
Process
All of the following issues, when completed, should be opened against the feature branch, 2893/multi-tenancy-v1, and can be marked completed in the parent issue here once merged in.
Once multi-tenancy is fully implemented in the feature branch, the feature branch may be merged into main.
Context
Planning Document
Currently, Rafiki can only be used by a single ASE. We want that a single Rafiki instance to be able to handle multiple tenants (ASEs).
Process
All of the following issues, when completed, should be opened against the feature branch,
2893/multi-tenancy-v1
, and can be marked completed in the parent issue here once merged in.Once multi-tenancy is fully implemented in the feature branch, the feature branch may be merged into
main
.Feature Branch
Todos
Prerequisites
Database/Schema changes
backend
tenants table #3103tenantSettings
table in backend #3127auth
tenants table #3113Backend changes
backend
tenant service #3123backend
Admin Tenant API #3124Auth changes
auth
tenant service #3122auth
Tenant Admin Graphql API #3125Frontend changes
Deprecated Issues
tenantId
to fees #3032tenantId
to OP paths #2926tenantId
in Admin API calls #2929Backlog/Potential Future Changes
getOrCreateConnection
method in Database Connections Service #3105The text was updated successfully, but these errors were encountered: