fix(secrets): lazily adopt legacy keyring secrets on read with write-through (#1008) - #1016
Merged
Merged
Conversation
github-actions
Bot
added
bug
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.
Summary
Fixes #1008.
ConnectionSecretsStore.readForConnection, when either the password or connection string is not found under the namespaced key (e.g. because transient OS keyring locks or D-Bus timeouts interrupted the one-time DB upgrade migration), lazily check the legacy unnamespaced keys.ConnectionSecretsStore.deleteForConnection, also ensure legacy keys are cleaned up to prevent them from being resurrected.test/core/storage/local_db_profile_secrets_test.dartverifying on-demand lazy adoption and deletion.Closes #1008