A docker container network with Toxi-Proxy #362
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR adds Docker container network for integration testing with Toxi-Proxy.
The container network has a Styx as a proxy and an Apache as a static file server. A toxi-proxy is deployed to intercept all traffic between the two. The toxics can be configured in toxi-proxy configuration file, or in runtime using the toxi-proxy HTTP API etc.
The following ports are exposed to the host machine:
Styx configuration server configuration is mounted from host, from
styx-config/styxconf.ymlfile, and the origin file is instyx-config/origins.yml. By default, the styx configuration is set to monitor the origins file. Therefore the origins can be re-configured while the styx is running.