-
Notifications
You must be signed in to change notification settings - Fork 17
PM-25012: Cipher versioning data types #433
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
base: vault/cipher-versioning-with-data
Are you sure you want to change the base?
PM-25012: Cipher versioning data types #433
Conversation
New Issues (4)Checkmarx found the following issues in this Pull Request
|
@@ -279,7 +279,7 @@ impl Decryptable<KeyIds, SymmetricKeyId, Fido2CredentialFullView> for Fido2Crede | |||
|
|||
#[allow(missing_docs)] | |||
#[derive(Serialize, Deserialize, Debug, Clone)] | |||
#[serde(rename_all = "camelCase", deny_unknown_fields)] | |||
#[serde(rename_all = "camelCase")] |
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.
Are there any concerns / issues with allowing (and ignoring) unknown fields during deserialization? Removing this attribute from all the CipherType types drastically simplifies the extraction process.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## vault/cipher-versioning-with-data #433 +/- ##
====================================================================
Coverage ? 74.78%
====================================================================
Files ? 256
Lines ? 22400
Branches ? 0
====================================================================
Hits ? 16752
Misses ? 5648
Partials ? 0 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
🎟️ Tracking
PM-25012
📔 Objective
Moves the deserialization of the
data
object into the SDK - as part of running cipher migrations, the CipherType objects will be extracted instead of being passed in from the client.⏰ Reminders before review
team
🦮 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 confirmedissue 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