-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Adding cache for recording_encryption
resource
#55857
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: eriktate/sync-recording-encryption
Are you sure you want to change the base?
Adding cache for recording_encryption
resource
#55857
Conversation
c477750
to
9e0b61c
Compare
5f70d06
to
603dbde
Compare
9e0b61c
to
7032a39
Compare
3a22931
to
f704ea7
Compare
7032a39
to
8fe244f
Compare
f704ea7
to
a89de49
Compare
8fe244f
to
b6c22fe
Compare
25e862e
to
d40fb37
Compare
b6c22fe
to
7323861
Compare
41804ad
to
e9ec376
Compare
d4f3ac3
to
145dc0c
Compare
e9ec376
to
5d49ccd
Compare
145dc0c
to
4fc9628
Compare
fddaaf7
to
f6fc84e
Compare
4fc9628
to
5fb9b05
Compare
f6fc84e
to
f5e7591
Compare
5fb9b05
to
243c554
Compare
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.
Isn't this missing the parser to convert backend events into typed watch events?
6928e8d
to
9d9d44b
Compare
9d9d44b
to
9bc2d2c
Compare
It was actually included in an earlier PR: https://github.com/gravitational/teleport/blob/master/lib/services/local/recording_encryption.go#L95-L128 |
This adds cache support for the recording encryption resource. The only operation that makes use of the cache is decryption during replay which is powered by FindDecryptionKey