From ff87c487c8d7fa4aa396d0c8ee1e107f6b267751 Mon Sep 17 00:00:00 2001 From: kevgliss Date: Mon, 28 Aug 2017 17:57:39 -0700 Subject: [PATCH] It's too expensive to attempt to load all certificates associated with a given notification. Some queries such as `default` are associated with a large number of certificates. We have little control over when these objects are loaded, but when marshalled they are lazyloaded via SQLAlachemy. If a user needs to get all the certificates associated with a certificate they should use the /notifications//certificates endpoints that support pagination. (#891) --- lemur/notifications/schemas.py | 1 - 1 file changed, 1 deletion(-) diff --git a/lemur/notifications/schemas.py b/lemur/notifications/schemas.py index 12242284..3a772d78 100644 --- a/lemur/notifications/schemas.py +++ b/lemur/notifications/schemas.py @@ -26,7 +26,6 @@ class NotificationOutputSchema(LemurOutputSchema): active = fields.Boolean() options = fields.List(fields.Dict()) plugin = fields.Nested(PluginOutputSchema) - certificates = fields.Nested(AssociatedCertificateSchema, many=True, missing=[]) @post_dump def fill_object(self, data):