Massive thanks to @kapishmalik and @petkostas! Hoverfly's simulation schema has been bumped to v5.2 to support these new awesome matchers 🚀 :
Most excitingly new schema lets you do matcher chaining to create powerful matchers, for example, you can match a JWT token's payload containing a name JSON field with the value "John Doe", and the JWT token is present in a URL encoded form.
"body": [{
"matcher": "form",
"value": {
"client_assertion": [{
"matcher": "jwt",
"value": "{\"header\":{\"alg\":\"HS256\"},\"payload\":{}}",
"doMatch": {
"matcher": "jsonpath",
"value": "$.payload",
"doMatch": {
"matcher": "jsonpath",
"value": "$.name",
"doMatch": {
"matcher": "exact",
"value": "John Doe"
}
}
}
}]
}
}]
For more info, please check out the doc here.
v5.2 simulation also supports declaring global literals and variables for templated response. These are the constants and helper methods which you want to re-use for templating throughout a simulation.
Other changes include Go version upgrade to 1.18 and other dependency bumps (thanks @joobus )
-https-only
and proxy-auth
flags.Pre-load cache bugfix: https://github.com/SpectoLabs/hoverfly/issues/1009
Supports remote response body file: doc (thanks to @ns3777k)
Also build Hoverfly for Linux/ARM64 as requested by the community.
Simulation schema is upgraded to v5.1
to support the following new features (a big thanks to @ns3777k):
The binary size is up a few MBs after switching to go mod since v1.2.0
, so this release strip off the debugger info to squeeze it down a little bit while we come up with a plan for hoverfly to lose some weight.
Hoverfly is migrated to Go 1.14 and using Go Modules to manage its dependencies.
Feature-wise, thanks to @ri-tatsu, logging to a file is now supported:
hoverfly -logs-output=file
A new matcher type xmlTemplated
is added for XML loose matching with templated functions: https://github.com/SpectoLabs/hoverfly/pull/939
A universal date time templating helper is added:
{{ now "<offset>" "<format>" }}
It generates current date time with an offset in any custom format or Unix timestamp. More info can be found in the doc.
Thanks to @kulaginds' PR, you can now use templating functions in the response headers.
Hoverfly by default ignores repeated requests when capturing. Using the following flag, you can set Hoverfly to capture the new request-response pair by overwriting the old one.
hoverctl mode capture --overwrite-duplicate
Thanks to @aosavitski's PR, the performance of stateful simulation has been improved.
This release also fixed the following bugs:
https://github.com/SpectoLabs/hoverfly/issues/868
https://github.com/SpectoLabs/hoverfly/issues/865
You can now enable Cross-Origin Resource Sharing (CORS) support on hoverfly. Your web application running on the browser can make requests to Hoverfly even it’s not on the same domain.
hoverfly -cors
or
hoverctl start --cors
For more information, please see the docs.
Some users experience slow import for large simulation file (a few hundred MBs with lots of pairs), you can speed it up by disabling the duplicate request checking feature:
hoverfly -no-import-check
or
hoverctl start --no-import-check
A response proxied by Hoverfly contains header Hoverfly: Was-Here
. In this release, we are adding Hoverfly: Forwarded
to it if a request is not simulated but forwarded to the remote service in SPY
mode.
We have added a new helper method for string find and replace:
{{ replace string oldValue newValue }}
For example, you can solve the problem in issue https://github.com/SpectoLabs/hoverfly/issues/841 with this templating function which replaces all occurrences of "_token" in the query params with an empty string.
{{ replace Request.QueryParam.access_token.[0] "_token" "" }}
You can now import multiple simulations when you start hoverfly using hoverctl
:
hoverctl start --import foo.json --import bar.json
This is equivalent to the following hoverfly
command:
hoverfly -import foo.json -import bar.json
You can also add additional simulations after hoverfly is started:
hoverctl simulation add foo.json bar.json
This release also fixes the following bugs:
After the previous two RC versions, we are so excited to finally release Hoverfly v1.0.0. We really appreciate all the contributions and feedback from the community!
A big thanks to @dilitvinov, a new matcher (jsonPartial
) is available to let you partially match a JSON document. You can find out more here here.
Some APIs use HTTP response trailers, and we have implemented a solution to capture them as normal headers:
"response" : {
"headers" : {
"Trailer": ["X-Streaming-Error"],
"X-Streaming-Error" : [ "Connection Closed" ]
}
}
Hoverfly Helm chart has been accepted into the official Helm incubator repository.
You can simply run the following command to deploy Hoverfly into your Kubernetes cluster:
helm install incubator/hoverfly
You can find more details in the doc.
Thanks to @rusenask, the Hoverfly v1.0.0 Docker image will be much slimmer as it based on Alpine, and the Dockerfile uses multi-stage build.
This release improves performance. These improvements will save both CPU time and reduce latency, in some cases by a significant margin. Thanks to the Hoverfly community for their assistance in identifying and fixing these issues.
$ hoverfly -cache-size 100
Fixed an issue which prevented hoverctl controlling a remote hoverfly running in a Docker container: https://github.com/SpectoLabs/hoverfly/issues/801