📤 implement egress proxy

[jadudm]

At a glance

In order to deploy in cloud.gov
as a developer
I want an egress proxy

Acceptance Criteria

We use DRY behavior-driven development wherever possible.

then...

Beta Give feedback

1. [a thing happens]

Shepherd

• UX shepherd:
• Design shepherd:
• Engineering shepherd:

Background

We can only talk to the outside world via an egress proxy.

Therefore, we need one.

It will need to get a rendered list of all of the domains that we're going to talk to. So, some more work around the sites that are being crawled needs to be done.

Security Considerations

Required per CM-4.

This is all about egress control, so it is very much about security. Fundamental controls.

---

Process checklist

• Has a clear story statement
• Can reasonably be done in a few days (otherwise, split this up!)
• Shepherds have been identified
• UX youexes all the things
• Design designs all the things
• Engineering engineers all the things
• Meets acceptance criteria
• Meets QASP conditions
• Presented in a review
• Includes screenshots or references to artifacts
• Tagged with the sprint where it was finished
• Archived

If there's UI...

• Screen reader - Listen to the experience with a screen reader extension, ensure the information presented in order
• Keyboard navigation - Run through acceptance criteria with keyboard tabs, ensure it works.
• Text scaling - Adjust viewport to 1280 pixels wide and zoom to 200%, ensure everything renders as expected. Document 400% zoom issues with USWDS if appropriate.