-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Record multiple external services #299
Comments
Thanks! Yes, it is possible to record against multiple targets by configuring a proxy stub mapping against each of them via the API rather than via the --proxy-all param (which actually just creates a single proxy mapping internally). |
hi @tomakehurst . I am also attempting to record against multiple services. However it is not clear to me how to do it. The only way I can record is against one service via --proxyAll. Could you give me an example on how to do the above please? |
hi @tomakehurst My API has multiple exernal API calls and i need to mock that by recording them. I am getting unauthorised error. However if i make calls to the external apis directly i am able to record them could you please help. |
Hi; I just used wiremock to do some load testing in docker and it worked great; FWIW being able to record multiple urls at once would be nice, e.g. in Doing something like Great tool; thanks! |
How to record against multiple targets by configuring a proxy stub mapping against each of them:
|
For an exemple on how to record and replay multiple external services check this out https://github.com/educostadev/wiremock |
Hi,
First of all congratulations for this great library. Its simple to use, good documentation and more importantly: it works! :)
My issue is related with the fact that I need to record not one external service but many of them. It seems that the wiremock-standalone just has the option to setup one proxy using the
--proxy-all
switch. Is it possible to record with my own defined stubs? If no, is there any other to achieve this?Thanks a lot!
Leo
The text was updated successfully, but these errors were encountered: