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

Prod: Configure the send email notification delivery status to VA Profile #1780

Closed
6 of 9 tasks
MackHalliday opened this issue May 2, 2024 · 9 comments · Fixed by #2018
Closed
6 of 9 tasks

Prod: Configure the send email notification delivery status to VA Profile #1780

MackHalliday opened this issue May 2, 2024 · 9 comments · Fixed by #2018

Comments

@MackHalliday
Copy link

MackHalliday commented May 2, 2024

User Story - Business Need

We want to improve the management and reliability of email data within the VA system in collaboration with VA Profile by

  • Tracking delivered and bounced emails, specifically identifying hard bounces (permanent failures) and soft bounces (temporary issues).
  • VA Notify will support VA Profile by providing real-time data on email deliverability.
  • Utilizing existing infrastructure and celery tasks to minimize new development efforts.

  • Ticket is understood, and QA has been contacted (if the ticket has a QA label).

User Story(ies)

As a VA Notify Developer,
I want properly configure and test new feature to send email notification delivery status to VA Profile in the Production environment.
So that we can ensure the new feature functions as expected in the Production environment.

Additional Info and Resources

Engineering Checklist

  • Confirm bearer token ssm parameter is populated for prod
  • Enable feature flag in Production environment
  • Coordinate with VA Profile to conduct integration tests
    • Verify that POST requests send accurate and complete email delivery status data.
    • Ensure error handling processes are properly logging and managing errors.
    • Obtain QA approval after successful testing of all scenarios in the Production environment. QA not necessary on this ticket.
  • Update the Slide deck with the key win and a demo slide

Acceptance Criteria

  • The new features can send delivery status data on ALL email notifications
  • Any errors, whether expected or unexpected, are logged and handled gracefully

QA Considerations

  • Shadow the VAProfile testing
@MackHalliday MackHalliday changed the title Copy of Staging: Configure and test new feature to send email notification delivery status to VA Profile in Staging Production: Configure and test new feature to send email notification delivery status to VA Profile in Production May 2, 2024
@cris-oddball cris-oddball changed the title Production: Configure and test new feature to send email notification delivery status to VA Profile in Production Prod: Configure the send email notification delivery status to VA Profile May 2, 2024
@cris-oddball
Copy link

@mjones-oddball
Copy link

Marked as blocked because we can't do this ticket until VA Profile creates and provides their prod endpoint. There's also a dependency on finishing the integration in QA (Staging/Perf) first.

@k-macmillan
Copy link
Member

Okay to keep.

@kbelikova-oddball
Copy link

VA Profile's Prod launch date is Sept 10

@mjones-oddball
Copy link

This is no longer blocked. @EvanParish has the info for the prod endpoint.

@EvanParish
Copy link

Yes. The endpoint is the same and the token has been placed in ssm.

@EvanParish
Copy link

I think this was accidentally closed on the merge. I will verify with VA Profile that this is working before closing the ticket. The feature flag has been enabled and the code is on it's way through the environments.

@EvanParish
Copy link

EvanParish commented Sep 26, 2024

It looks like we are getting a 200 response back from VA Profile, so that's a good sign!
Just waiting on confirmation from Ian on the VA Profile team to confirm everything is looking good to them.

image.png

@EvanParish
Copy link

It looks like everything is good on the VA Profile side as well. Done!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment