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

Don't create root workspace in database in migration tool #1176

Merged
merged 1 commit into from
Sep 6, 2024

Conversation

lpichler
Copy link
Contributor

  • existence of root workspace in RBAC doesn't have usage and it becomes prerequisite to enable dual writes

    • this means that migration has to be done first before enabling dual writes
  • it adds complexity: it is need to create root workspace when new organisation needs to be created rbac

  • Name of root workspace could be determined from org_id only which simplifies code and reduces issues which be caused by existence/non-existence of root workspace

Copy link
Contributor

@coderbydesign coderbydesign left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving based on the collab this morning, knowing we'll likely need to consider the IDs being used for all workspace relations moving forward.

@lpichler lpichler force-pushed the dont_create_root_workspace_record_in_db branch from 26a3183 to ec963a6 Compare August 28, 2024 09:26
@astrozzc astrozzc force-pushed the dont_create_root_workspace_record_in_db branch 2 times, most recently from 52f12cd to c3060af Compare September 6, 2024 17:53
@astrozzc astrozzc force-pushed the dont_create_root_workspace_record_in_db branch from c3060af to 340740c Compare September 6, 2024 17:58
@astrozzc astrozzc merged commit 3b3fe4e into master Sep 6, 2024
4 checks passed
@astrozzc astrozzc deleted the dont_create_root_workspace_record_in_db branch September 6, 2024 18:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants