Add support to proxy outbound requests from Synapse in tests #18158
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add support to proxy outbound requests from Synapse in tests. Adds new environment variables that can be used with the Docker image (
SYNAPSE_HTTP_PROXY
/SYNAPSE_HTTPS_PROXY
/SYNAPSE_NO_PROXY
)Useful for things like the Secure Border Gateway
Why is this necessary?
You can already configure the
HTTP_PROXY
/HTTPS_PROXY
environment variables to proxy outbound requests but setting this globally in the Docker image affects all processes which isn't always desirable or workable in the case where the proxy is running in the Docker image itself (because the Debian packages will fail to download because the proxy isn't up and running yet) . Adding Synapse specific environment variables (SYNAPSE_HTTP_PROXY
/SYNAPSE_HTTPS_PROXY
/SYNAPSE_NO_PROXY
) makes things much more targetable.Pull Request Checklist
EventStore
toEventWorkerStore
.".code blocks
.(run the linters)