v1.8.0

What's Changed

• Add -log-no-quotes CLI flag to disable quoting/escaping of fields in logs by @benediktwerner in #1115
• Fix matching score bug for body matcher by @tommysitu in #1116
• A new response Templating function to extract data from journal by @kapishmalik. More details can be found in the doc.

New Contributors

• @benediktwerner made their first contribution in #1115

Full Changelog: v1.7.0...v1.8.0

v1.7.0

What's Changed

• Remove support for deprecatedQuery by @tommysitu in #1112
• Support compound param query by @tommysitu in #1114

and most importantly, supporting CSV data for response templating!! Please check out the doc here. Great work by @kapishmalik 👏

Full Changelog: v1.6.3...v1.7.0

v1.6.3

Minor bug fixes for journal search endpoint.

v1.6.2

Minor bug fix and security update.

v1.6.1

Small release with a security update and revamp of the Hoverfly readthedocs with a more recent version of Sphinx v5.3.0.

v1.6.0

You can specify and invoke a callback for an HTTP response using post-serve action. More details can be found in this tutorial.

This release also includes a journal bug fix for handling binary data in the request body.

v1.5.3

Security updates.

v1.5.2

Bug fixes related to the Form and Array matcher. Thanks to @kapishmalik

v1.5.1

Bug fix for URL-encoded form request data capturing.

v1.5.0

Massive thanks to @kapishmalik and @petkostas! Hoverfly's simulation schema has been bumped to v5.2 to support these new awesome matchers 🚀 :

• Array matcher: supports loose matching for array values, and this will be the default matcher for multi-value query param or header in captured data.
• Form matcher: matches request payload with URL encoded form.
• JWT matcher: has a built-in JWT parser, and lets you match JWT with its decoded JSON form directly.

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 )