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.

Sign up for GitHub

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

Jump to bottom

Design strategy for data migration (RFC) #5350

Closed

FirelightFlagboy opened this issue Sep 25, 2023 · 1 comment · Fixed by #5303

Assignees

Labels

A-Docs I-API

Contributor

FirelightFlagboy commented Sep 25, 2023

No description provided.

FirelightFlagboy mentioned this issue

V3 Roadmap #5137

Closed

37 tasks

FirelightFlagboy linked a pull request

that will close this issue

Add RFC 1005: Realm key rotation #5303

Merged

FirelightFlagboy assigned touilleMan

FirelightFlagboy added A-Docs I-API labels

touilleMan closed this as completed in #5303

Contributor

mmmarcos commented Feb 27, 2024

Comment on database migration from #5137:

Organizations on the parsec-v2 database (SaaS) must be migrated to the new parsec-v3 database
Ideally, we should be able to simply clone the database and then apply migration script

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment