-
Notifications
You must be signed in to change notification settings - Fork 2
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
Create an egress proxy module #53
Conversation
Co-authored-by: Zachary Rollyson <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[I feel like my IQ has dropped 100 points since I wrote this... Really proud of the result, just not sure if I'd have the grit to figure it out if I had to today.]
I think there was a Mermaid diagram in the source repo... Am I misremembering? Or is it in the cg-egress-proxy
repo? Either way I think it should be included here too. Other than that, these are good additions, and I wouldn't hold up the merge for wont of the diagram.
you're not misremembering, but it is the exact mermaid diagram that's in cg-egress-proxy's README. I'm going to merge this and we'll improve docs/diagrams in due course |
🎫 Addresses issue: #42
closes #42
🛠 Summary of changes
allowports
variable to customize the ports caddy is listening onspace_name
to the cg_space output variables to ease use of both cg_space and egress_proxy modules together📜 Testing Plan
Implemented and deployed an app using this module: GSA-TTS/continuous-assessment-poc#45
Deploy action: https://github.com/GSA-TTS/continuous-assessment-poc/actions/runs/11277289453