-
Notifications
You must be signed in to change notification settings - Fork 15
Open
Description
The encryption schema is currently being loaded multiple time during the lambda invocation. Ideally this schema should be loaded once and then re-used by the methods that need it.
Currently it is initialized in the documentdb-encryption-service.js via loadCustomEncryptionSchema() and in prisma.js also via loadCustomEncryptionSchema()
Frigg logs:
[Frigg] Registered custom encryption schema for models: User
[Frigg] Field-level encryption enabled using AES
[Frigg] Registered custom encryption schema for models: User
[Frigg] Registered custom encryption schema for models: User
[Frigg] Registered custom encryption schema for models: User
[Frigg] Registered custom encryption schema for models: User
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels