TheUsharik
03/07/2023, 4:18 PMrepeatsAsScenarios
option if running WireMock as standalone app in docker container. Looks like this option is set to false
by default because in the logs I see messages like
Not recording mapping for /some/url as this has already been received
In my case it's crucial to record and replay all such queries as a scenario. What can I do here?Rob Elliot
03/07/2023, 4:27 PMrepeatsAsScenarios
is set when you start recording. How are you putting WireMock into record mode? Using the UI, or the Java DSL, or using an HTTP client?
If via an HTTP Client, try this:
POST /__admin/recordings/start
{
"targetBaseUrl": "<http://example.mocklab.io>",
"repeatsAsScenarios": true
}
TheUsharik
03/07/2023, 4:28 PM--record-mappings
options as a parameter to the docker container
fusion_wiremock:
image: wiremock/wiremock:latest
ports:
- 8080:8080
- 8443:8443
volumes:
- ./wiremock-recordings:/home/wiremock
command: ['--verbose', '--https-port=8443', '--print-all-network-traffic', '--record-mappings', '--proxy-all=<https://someurl>']
Rob Elliot
03/07/2023, 4:29 PM--record-mappings
option beyond what you've used.
See https://wiremock.org/docs/record-playback/TheUsharik
03/07/2023, 4:36 PMRob Elliot
03/07/2023, 4:52 PMTheUsharik
03/07/2023, 4:53 PMRob Elliot
03/07/2023, 5:06 PMTheUsharik
03/07/2023, 5:37 PMrepeatsAsScenarios
without starting of new recording. Which endpoint shall I call?Rob Elliot
03/07/2023, 5:46 PM'--record-mappings', '--proxy-all=<https://someurl>'
and then make the HTTP request:
POST /__admin/recordings/start
{
"targetBaseUrl": "<http://example.mocklab.io>",
"repeatsAsScenarios": true
}
TheUsharik
03/07/2023, 5:47 PMRob Elliot
03/07/2023, 6:04 PMTheUsharik
03/07/2023, 6:05 PM