-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[PM-13706] Add repository + stored procedures for private key regeneration #4898
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #4898 +/- ##
==========================================
- Coverage 43.09% 43.06% -0.03%
==========================================
Files 1414 1417 +3
Lines 64808 64849 +41
Branches 5925 5927 +2
==========================================
+ Hits 27929 27930 +1
- Misses 35645 35685 +40
Partials 1234 1234 ☔ View full report in Codecov by Sentry. 🚨 Try these New Features:
|
New Issues
Fixed Issues
|
src/Infrastructure.Dapper/KeyManagement/Repositories/UserAsymmetricKeysRepository.cs
Outdated
Show resolved
Hide resolved
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.
LGTM
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.
lgtm
ff8e01e
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.
lgtm
🎟️ Tracking
https://bitwarden.atlassian.net/browse/PM-13706
📔 Objective
The purpose of this PR is to add the database stored procedure and repository layer for the private key regeneration project.
This initial phase will only target users not in organizations and without emergency access setup.
In future PRs, the database operations will expand to handle these cases.
📸 Screenshots
⏰ Reminders before review
🦮 Reviewer guidelines
:+1:
) or similar for great changes:memo:
) or ℹ️ (:information_source:
) for notes or general info:question:
) for questions:thinking:
) or 💭 (:thought_balloon:
) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion:art:
) for suggestions / improvements:x:
) or:warning:
) for more significant problems or concerns needing attention:seedling:
) or ♻️ (:recycle:
) for future improvements or indications of technical debt:pick:
) for minor or nitpick changes