-
Notifications
You must be signed in to change notification settings - Fork 5
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
Adding more work on salt encryption #353
base: main
Are you sure you want to change the base?
Conversation
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 you still adding tests for these?
|
||
@Override | ||
public StoreReader<Collection<RotatingSaltProvider.SaltSnapshot>> getReader(Integer siteId) { | ||
return null; |
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.
Should these methods not throw, rather than return null? If we don't expect them to be called, they should at least throw so we catch the error earlier.
Or do we divide the interface so that the methods are not required here?
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.
Throwing would change the interface too. But I think splitting it up would also be annoying.
I am thinking when we continue with Admin rework, we migrate salts to follow the pattern of our other files and we can fill these in then.
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.
Ok, lets leave it as, but add logging (at WARN level) to indicate the method is being called.
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.
Small comment about adding some logging
…ABTechLab/uid2-admin into cbc-UID2-4571-cloud-encryption-cleanup
No description provided.