Implement EncryptedData struct #3302
Merged
Conversation
This file contains 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
Relates to #3292 Adds a new struct for representing an encrypted piece of data. As per @jhrozek's design doc, this struct will be serialized and stored in the database. This will be implemented in a later PR. For now, the Engine interface has been refactored to accept and return instances of these structs.
stacklokbot
reviewed
May 10, 2024
stacklokbot
reviewed
May 10, 2024
stacklokbot
reviewed
May 10, 2024
stacklokbot
reviewed
May 10, 2024
stacklokbot
reviewed
May 10, 2024
stacklokbot
reviewed
May 13, 2024
stacklokbot
reviewed
May 13, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Relates to #3303
Adds a new struct for representing an encrypted piece of data. As per @jhrozek's design doc, this struct will be serialized and stored in the database. This will be implemented in a later PR. For now, the Engine interface has been refactored to accept and return instances of these structs.
As per the design doc, I had originally intended to represent this struct as a protobuf struct. However, I realized that it would be far more straight forward to use a struct + JSON serialization for a type which will not be exposed by our API.
Tested locally.
Summary
Provide a brief overview of the changes and the issue being addressed.
Explain the rationale and any background necessary for understanding the changes.
List dependencies required by this change, if any.
Fixes #(related issue)
Change Type
Mark the type of change your PR introduces:
Testing
Outline how the changes were tested, including steps to reproduce and any relevant configurations.
Attach screenshots if helpful.
Review Checklist: