I am building a proxy service to record and play responses from the web using WireMock. I have recently discovered that these two modes are separate, so am attempting to build a small set of Docker containers to run these services in parallel.
Briefly, my plan is to set up one WireMock for recording, and then have another instance (on a different port) for playback. I'll periodically copy the mappings from one to the other on a cron, and then send the reset API call to the playback instance to reload new definitions.
So, I am working on the recorder presently. An easy way to record from a specific site is to do this:
java -jar wiremock-standalone-2.4.1.jar \
--port 8080 \
--proxy-all="http://www.example.com/" \
--record-mappings \
--verbose
However, that locks a long-running instance to www.example.com, when in fact I want it to record anything I send to it. Using --proxy-all without a parameter does not work (it results in 500 errors in the HTTP client, presumably emitted by WireMock itself).
Omitting --proxy-all on the other hand results in a 404, since presumably WireMock does not know where to go. I would therefore like to do something like:
--proxy-all=*
I can't see any docs to say this is supported on the command line, so I wonder if the admin API supports this? The alternative is for me to build my own API to stop and restart WireMock on a specified proxy URL, but if that is already implemented I would rather not re-invent the wheel.
As I said on my other question, using Mountebank instead may be an option, since it seems to have an API for this. However that looks more involved, and since I am 90% of the way there with WireMock, I am minded to stick with it if I can.
