Releases: SpectoLabs/hoverfly
v0.7.0
Greetings!
We've been busy adding new features to Hoverfly, as well as developing tools to support the use of Hoverfly.
Hoverctl
We have created a new command line interface for Hoverfly. This allows for the management of local and remote Hoverfly instances. Using hoverctl, you can start and stop instances of Hoverfly, and manage Hoverfly data. You can export your simulations and then share them on SpectoLab, an API simulation repository for sharing and retrieving simulations. SpectoLab is currently in private beta, but you can request access. Hoverctl will still work with Hoverfly, even if you don't have access to SpectoLab.
For more information on hoverctl: hoverctl reference
Install script
Run the following command to install and set up Hoverfly and hoverctl:
curl -o install.sh https://storage.googleapis.com/specto-binaries/install.sh && bash install.sh
Add response delays (without using middleware)
We noticed that a common usage of middleware was to introduce response delays to simulations, so we've added the ability to set response delays in Hoverfly without the need for middleware. Hoverfly uses a regex to match against a request, opening up the opportunity to add different delays to different hosts.
For more information on response delays: Simulating service latency
Run Hoverfly as a webserver
We also got feedback that running Hoverfly as a proxy was not always desirable (or even possible), especially when simulations have been recorded previously and all you need is simulate mode. Now Hoverfly can run as a webserver, allowing you to point your application directly at Hoverfly without having to configure a proxy. Currently this only works via HTTP.
For more information on running Hoverfly as a webserver: Server type
Other stuff
Also, this release introduces a new repository structure. This was mainly due to the introduction of hoverctl. The end result is a much tidier repository that makes it easy to run different suites of functional tests.
v0.6.0
Its time for a new minor version of Hoverfly.
Why have we gone from v0.5.17 to v0.6.0?
We made a slight change to the structure of payloads. We added a new field to indicate whether or not the body needs to be base64-encoded. The reason being that during the export and import process, any binary body data in a response would get lost due to being parsed to Unicode characters.
You can find out more about this change here. If you are trying to read or write binary data to the response body in your middleware, find out more here.
In this release, we have also introduced Ginkgo and Gomega to help us functionally test Hoverfly, which in turn has enabled us to start to modularize the codebase.
v0.5.17
Next version of UI and improved documentation
v0.5.16
v0.5.15
- BoltDB backend moved to separate package, currently used for requests/responses and metadata storage.
- Request body is now being minified before creating unique fingerprint ID to remove all spaces/new line symbols for JSON and XML content types.
- Destination can now be updated through API (restarts proxy goroutine)