-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
feat(core): add keys and key-sets entity #9737
Conversation
cf8b2b7
to
a635c5b
Compare
function key_sets:truncate() | ||
return self.super.truncate(self) | ||
end |
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.
Why do we need all the method redefinitions on this file (and on keys)?
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.
A matter of taste I guess. Some of the methods are generated based on presence of certain entity fields. Explicitly defining the methods, even if these are just a pass-through, helps with understanding the functionality that this dao provides.
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.
Signed-off-by: Joshua Schmid <jaiks@posteo.de>
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.
Let's move on with this, thanks @jschmid1.
counterpart to Kong/kong#9737
Supersedes: #9677
This is ready for a first round of reviews.
Summary
This PR adds support for managing asymmetric keys in various formats (JWK, PEM). It adds two new entities
that accept the mentioned formats.
Full changelog
Missing things:
or skip tests for itSigned-off-by: Joshua Schmid jaiks@posteo.de