Skip to content
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

Expose Toxiproxy control port and proxy name #3454

Merged
merged 2 commits into from
Dec 10, 2020
Merged

Expose Toxiproxy control port and proxy name #3454

merged 2 commits into from
Dec 10, 2020

Conversation

aartigao
Copy link
Contributor

@aartigao aartigao commented Nov 9, 2020

Fixes #3453

In order to work with and external Toxiproxy client we need the control port to get the mapped port and the proxy names to interact with.

In order to work with and external Toxiproxy client we need the control
port to get the mapped port and the proxy names to interact with.
Hidden the port constant again and created accessor for Toxiproxy
mapped control port.
@aartigao aartigao requested a review from bsideup November 9, 2020 15:19
@sullis
Copy link
Contributor

sullis commented Nov 22, 2020

LGTM

@bsideup bsideup added this to the 1.15.1 milestone Dec 10, 2020
@bsideup bsideup merged commit af678a3 into testcontainers:master Dec 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Toxiproxy cut connection behavior
3 participants