CORE-266: use GroupAccessRequestNotificationV2 #1627
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ticket: https://broadworkbench.atlassian.net/browse/CORE-266
What:
When sending a group access request notification, use
GroupAccessRequestNotificationV2
instead of the deprecatedGroupAccessRequestNotification
. This enforces, in code, that notifications only use a single reply-to address.Context of the overall rollout plan to adopt the SendGrid v3 APIs by February 10:
sendgrid-java
and v3 APIsGroupAccessRequestNotification
used by Sam which allows multiple reply-tos; provide a replacementGroupAccessRequestNotificationV2
that only allows a single reply-to. See CORE-266: enforce a single reply-to address on group-access-request notifications workbench-libs#1717 (this PR)GroupAccessRequestNotificationV2
model in Thurloe. See CORE-235: support GroupAccessRequestNotificationV2 notifications thurloe#372GroupAccessRequestNotificationV2
model in Sam. After this step, Thurloe would no longer ignore the reply-to value sent by Sam; Sam would once again be in control of the reply-to.GroupAccessRequestNotification
from ThurloeGroupAccessRequestNotification
from workbench-libsPR checklist