Allow custom port values in egress proxy

GSA / notifications-api

The API powering Notify.gov

Other

10 stars 1 forks source link

Allow custom port values in egress proxy #393

Closed stvnrlly closed 1 month ago

stvnrlly commented 1 year ago

This recently changed upstream. We either need to:

Find a way to inject our own environment variables at deploy
Fork the project and set our own value

Apparently, forking is expected. However, it'd be nice if we can find a way to continue sharing a codebase that's otherwise working perfectly for us.

VRagulina commented 6 months ago

Could be assigned to 18F engineer

ccostino commented 2 months ago

@stvnrlly, @jskinne3 and I will catch up with you about this soon to get more clarity on the issue and what we ought to be doing here. :-)

terrazoon commented 1 month ago

Likely requires permissions contractors don't currently have.

stvnrlly commented 1 month ago

This has been resolved on the egress proxy side! With the no_proxy setting, internal routings can avoid the proxy all together, which makes sense as they're never leaving cloud.gov.