v2.2.0
This is A Big Release!
This release has taken a long time to get out, but it's a game changer. Significant parts of mountebank have been re-architected to allow all operations to be persisted to the file system in real time. This solves a long-standing performance problem when dealing with a lot of test data (for example, during proxy recording or playback)
New Features
- The
--datadir
option allows all operations to be persisted real time, supporting constant performance regardless of the amount of test data. This also allows multiple hosts running the same imposter behind a load balancer, with all processes sharing the same state. - Running
mb
with the--debug
option now also records the response configuration that generated the response and the overall processing time to transform the request into the response. - Added an example Dockerfile
Bug Fixes
- You can now change the
state
variable passed into predicate injection - Fixed predicate matching for Cyrillic characters
- Fixed some documentation that still used the old injection format
- Fix issue where shellTransform limited buffer size of response
- Expanded the list of MIME types mountebank recognizes as binary during HTTP proxying
Contributors
Many thanks to the following kind folks for help with this release, either through bug reports, suggestions, or direct code contributions:
- George Tseres
Install
npm install -g mountebank@2.2.0
or:
Option | node.js required? | sudo required? | links | Description |
---|---|---|---|---|
Self-contained archives | No | No | Simply unpack and run mb from inside |
|
OS-specific packages | No | Yes | Puts mb at /usr/local/bin , which is generally in the PATH . |
|
source tarball | Yes | No | source tarball if you roll that way. |
Windows path limitations
*mountebank wishes very much for your Windows experience to be hassle-free, but he is simply not qualified to address a particular constraint of Windows Explorer. For legacy reasons, some Windows applications, including most notably Windows Explorer, have a maximum number of characters allowed in a path of 260 characters. As mountebank writes these words, the longest path he includes in the zip files is around 175 characters. The zip file name, which is likely to represent itself as two nested directories if you use the defaults to unzip it, will be around 25 characters. That gives you very little wiggle room. If you unzip the file in your users directory, you may very likely get an error because of this constraint.
The following solutions will all work:
- Unzip to the root of your C: drive (or a similar small path)
- Use 7zip to unzip the file instead of Windows Explorer
- Use
npm
to install mountebank instead of the zip file