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
This appends the supplied simulation JSON to the existing simulation data in Hoverfly. Any pair that has request data identical to the existing ones will not be added.
As per the documentation POST adds the supplied JSON, but lets say I have need to overwrite the existing content just for single request match NOT the whole simulations set, and API suitable for just this will be helpful.
We are looking for alternative to our existing mock solution. So in hoverfly we are looking for a way to not bring down a service and also NOT overwrite the whole set, but for something which can support multiple team members to use the same service in their own way. And many a times we end up changing the stubbed data, so we can not afford to overwrite and disrupt others.
If you have more questions, please let me know.
The text was updated successfully, but these errors were encountered:
Hoverfly hardly takes any time to update the entire simulation data as it is in memory and takes exclusive locks before modifying the simulation data. It won't disrupt the other services but at times call will be slower.
You are probably asking for a PATCH call but there is no mechanism to identify that request/response pair.
This appends the supplied simulation JSON to the existing simulation data in Hoverfly. Any pair that has request data identical to the existing ones will not be added.
As per the documentation POST adds the supplied JSON, but lets say I have need to overwrite the existing content just for single request match NOT the whole simulations set, and API suitable for just this will be helpful.
We are looking for alternative to our existing mock solution. So in hoverfly we are looking for a way to not bring down a service and also NOT overwrite the whole set, but for something which can support multiple team members to use the same service in their own way. And many a times we end up changing the stubbed data, so we can not afford to overwrite and disrupt others.
If you have more questions, please let me know.
The text was updated successfully, but these errors were encountered: