-
Notifications
You must be signed in to change notification settings - Fork 31
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
version 2 of user/organization tenant account module - UN-1424 #432
base: main
Are you sure you want to change the base?
Conversation
backend/tenant_account_v2/migrations/0002_alter_organizationmember_organization_and_more.py
Outdated
Show resolved
Hide resolved
…ack/unstract into feat/MultiTenancyV2-tenant-account
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@muhammad-ali-e Model looks ok.
Assuming that DefaultOrganizationMixin
will provide organization
field for OrganizationMember
.
Ignoring duplication, as v1 will be deleted later. Also as mentioned, we can generate migrations once all v2 apps are ready.
|
|
|
||
|
||
class UserRole(Enum): | ||
USER = "user" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@muhammad-ali-e are these the roles configured at Auth0?
What
Created a new application with the same V1 methods, with some changes in the models.
Major Changes in this PR:
The remaining changes involve duplicating or copying existing methods from other parts of the application to ensure consistency and reduce redundancy.
Why
Can this PR break any existing features. If yes, please list possible items. If no, please explain why. (PS: Admins do not merge the PR without this section filled)
Database Migrations
Env Config
Relevant Docs
Related Issues or PRs
Dependencies Versions
Notes on Testing
Screenshots
Checklist
I have read and understood the Contribution Guidelines.