To work natively with no modifications of our stack, we'd need celery to support natively.
Or we find some other ways to bypass celery.
VALUE created by our solution
Increased message size within GCNotify for one-var notifications or others with partials with lots of information.
More stability as we do put batched notification (with bundles of 10s) into SQS and these can take over 256kb altogether.
Acceptance Criteria
[ ] Investigation and discovery work performed on best option to support AWS extended library -- do we use Celery? do we bypass it? do we implement it? 🤔💭
Description
As a user of GCNotify, I want to send a large email, So that I can provide all necessary information to my recipients.
As a system operator of GCNotify, I want to increase the message body size support, So that I can increase the reliability of the system.
WHY are we building?
WHAT are we building?
VALUE created by our solution
Acceptance Criteria
QA Steps