-
Notifications
You must be signed in to change notification settings - Fork 11
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(kas): collect metrics #1702
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.
Just some nits about cleaning up the imports.
examples/cmd/examples.go
Outdated
@@ -31,7 +31,7 @@ func init() { | |||
|
|||
func newSDK() (*sdk.SDK, error) { | |||
resolver.SetDefaultScheme("passthrough") | |||
opts := []sdk.Option{sdk.WithStoreCollectionHeaders()} |
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.
Is this causing failures in integration test?
examples/cmd/examples.go
Outdated
@@ -31,7 +31,7 @@ func init() { | |||
|
|||
func newSDK() (*sdk.SDK, error) { | |||
resolver.SetDefaultScheme("passthrough") | |||
opts := []sdk.Option{sdk.WithStoreCollectionHeaders()} | |||
opts := []sdk.Option{sdk.WithStoreCollectionHeaders(), sdk.WithInsecurePlaintextConn()} |
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.
you probably want to drop sdk.WithStoreCollectionHeaders().
There is no way to determine if a nanoTDF is part of a collection or not, with this option on, it will always assume its part of a collection.
Since you are decrypting the same nanoTDF, it will store the key with the header and future decrypts will skip the rewrap call.
It's probably best that you remove this option for benchmarking.
No description provided.