Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Turn on Virtual Deliverability Manager #108

Merged
merged 8 commits into from
Oct 2, 2024
Merged

Commits on Oct 1, 2024

  1. Require at least version 5.20 of the Terraform AWS provider

    Version 5.20 of the Terraform AWS provider is the first version
    to offer the aws_sesv2_account_vdm_attributes resource, which we
    require in this root module.
    jsf9k committed Oct 1, 2024
    Configuration menu
    Copy the full SHA
    9a431d2 View commit details
    Browse the repository at this point in the history
  2. Temporarily use a non-default branch of cisagov/terraform-state-read-…

    …role-tf-module
    
    This is being done for testing purposes and can be reverted once
    cisagov/terraform-state-read-role-tf-module#37 is merged.
    jsf9k committed Oct 1, 2024
    Configuration menu
    Copy the full SHA
    6c750ff View commit details
    Browse the repository at this point in the history
  3. Add VDM configuration to SES account

    VDM will show us some useful information about emails that bounced,
    such as the diagnostic code indicating the reason for the bounce.
    
    We don't care about the engagement metrics, since we don't care to
    track if users click the attachments we send.
    jsf9k committed Oct 1, 2024
    Configuration menu
    Copy the full SHA
    bb0062b View commit details
    Browse the repository at this point in the history
  4. Configuration menu
    Copy the full SHA
    a2626a1 View commit details
    Browse the repository at this point in the history
  5. Add ability to get message insights to the policy for managing the su…

    …ppression list
    
    This will allow suppression list managers to get a suppressed
    destination (which will include a message ID) and then get the
    insights for that particular message.  This will allow the suppression
    list managers to view, e.g., the diagnostic code associated with the
    bounce.
    jsf9k committed Oct 1, 2024
    Configuration menu
    Copy the full SHA
    c21da04 View commit details
    Browse the repository at this point in the history
  6. Add a comment re upgrading to aws_sesv2_email_identity

    This is something we should consider doing in the future, although I'm
    not sure it could be done non-destructively.
    jsf9k committed Oct 1, 2024
    Configuration menu
    Copy the full SHA
    5408f24 View commit details
    Browse the repository at this point in the history

Commits on Oct 2, 2024

  1. Configuration menu
    Copy the full SHA
    a97a68f View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    19e841e View commit details
    Browse the repository at this point in the history