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

Create Toxics at startup #16

Open
cbgbt opened this issue Aug 24, 2023 · 3 comments
Open

Create Toxics at startup #16

cbgbt opened this issue Aug 24, 2023 · 3 comments

Comments

@cbgbt
Copy link
Contributor

cbgbt commented Aug 24, 2023

Is your feature request related to a problem? Please describe.
It's slightly inconvenient to configure toxics after-the-fact with the client when proxies can be configured using a config file.

Describe the solution you'd like
This would be a clear departure from toxiproxy, but I wonder if it would make sense to allow creation of toxics via configuration as well.

Describe alternatives you've considered
None. The status quo works well.

@cbgbt
Copy link
Contributor Author

cbgbt commented Aug 24, 2023

I think this is also possible if I switch to using core for my use-case, so I have yet another work around. I'll leave the issue open in case you have any interest in discussing expanding ProxyConfig (or some other solution) for this.

@oguzbilgener
Copy link
Owner

Yeah, I also found it inconvenient to have to re-configure the toxics every time the server starts up.

Originally I left this project at feature parity, but I'm not against new useful features like this :)

@oguzbilgener
Copy link
Owner

The config file could be JSON, YAML or anything else that we could provide quick support with using a library.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants