You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From both documentation and code, it seems like it is not possible to create toxics at startup (e.g. via -config), during populate or when creating a proxy[1].
The only possible flow is:
Create the proxy
Add toxics via API
My question is: did I miss some trick/hack/undocumented way to create proxies and their toxics in one shot?
Use case:
I use toxiproxy to simulate systems with high latency links between servers.
So at startup, for each proxy I wish I could say something like:
Proxy <...> has latency 200ms +/- 20ms, 1% packet loss
It would be nice if these 'baseline' toxics could live in the configuration, so that one JSON file is self-contained and reproduces the full setup. Currently I need to run code after startup to create these toxics.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
From both documentation and code, it seems like it is not possible to create toxics at startup (e.g. via
-config
), during populate or when creating a proxy[1].The only possible flow is:
My question is: did I miss some trick/hack/undocumented way to create proxies and their toxics in one shot?
Use case:
I use toxiproxy to simulate systems with high latency links between servers.
So at startup, for each proxy I wish I could say something like:
It would be nice if these 'baseline' toxics could live in the configuration, so that one JSON file is self-contained and reproduces the full setup. Currently I need to run code after startup to create these toxics.
[1] #79
Beta Was this translation helpful? Give feedback.
All reactions