[PB-6505] Remove old key fields from UserSettings#2033
Draft
TamaraFinogina wants to merge 1 commit into
Draft
Conversation
Deploying drive-web with
|
| Latest commit: |
202ebf0
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://2279f842.drive-web.pages.dev |
| Branch Preview URL: | https://remove-old-key-fields.drive-web.pages.dev |
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR reduces the amount of data in UserSettings by removing old fields. Will help once we start encrypting it.
Related Issues
PB-6505
Related Pull Requests
Checklist
Testing Process
Check that backups work without problems. The login, workspace, etc. are less affected.
Additional Notes
We switched to keys in UserSettings over a year ago. There should be no users with an ongoing session without a Kyber keys or keys field.