This message was deleted.
# help
s
This message was deleted.
r
Could you elaborate a bit on what the problem is you are trying to solve?
m
An approach you could take, you could use IPtables to limit interactions/connections to your WireMock recorder. https://docs.docker.com/network/iptables/ Docker Docs has some examples you can use.
Or, if you want to be fancy, deploy this to Kubernetes, use a CNI like Cilium and use NetworkPolicy with a label-selector in case your WireMock pod gets re-deployed with a new IP.