Consider changes to SMTP Broker

[nickumia-reisys]

User Story

In order to handle new updates to the SMTP Broker, the Data.gov maintenance team wants to assess whether the new changes to the SMTP Broker are worth incorporating.

Acceptance Criteria

[ACs should be clearly demoable/verifiable whenever possible. Try specifying them using BDD.]

• GIVEN an assessment has been made
  WHEN the SMTP Broker is updated happens
  THEN the desired changes take effect.

Background

• Updates for Notify use cases GSA-TTS/datagov-brokerpak-smtp#18

Security Considerations (required)

May result in new permission for the SMTP Broker, but nothing out of the ordinary.

Sketch

• Decide whether we want the new features
  • If we DO NOT want the features,
    • Set enabled_feedback_notifications: false in the SMTP creation for catalog and inventory
  • If we DO want the features,
    • Update permissions for the SMTP broker in datagov-ssb
    • Optionally set enabled_feedback_notifications: true (the default is true, so it would just be documentation that this is enabled)

[jbrown-xentity]

Going to take initial mitigation steps, then delay the feature integration... cc @nickumia-reisys

[nickumia-reisys]

Mitigation steps complete ✔️

[nickumia-reisys]

Superseded by

• Update datagov-brokerpak-smtp #4232