v2.9.1 was released simply to fix a deployment version mismatch of v2.9.0; there are no other functional changes
npm install -g mountebank@2.9.1
]]>
Many thanks to the following kind folks for help with this release, either through bug reports, suggestions, or direct code contributions:
npm install -g mountebank@2.9.0
]]>
--datadir
Many thanks to the following kind folks for help with this release, either through bug reports, suggestions, or direct code contributions:
npm install -g mountebank@2.8.2
]]>
This release served only to fix a deployment issue. Please see v2.8.0 for release notes
]]>rejectUnauthorized
flag on
https servers to allow certificate validation.mb
is the only commandrequire
optimizations)apikey CLI parameter
for validationMany thanks to the following kind folks for help with this release, either through bug reports, suggestions, or direct code contributions:
npm install -g mountebank@2.8.0
]]>
Many thanks to the following kind folks for help with this release, either through bug reports, suggestions, or direct code contributions:
npm install -g mountebank@2.7.0
]]>
fault
response type
that simulates network failures.ignore
field to predicateGenerators
to enable you
to exclude certain request fields from the generated predicateMany thanks to the following kind folks for help with this release, either through bug reports, suggestions, or direct code contributions:
npm install -g mountebank@2.6.0
]]>
This release is largely centered around modernizing the codebase and simplifying the build process. That involved removing some previously supported install options:
CMD
instead of
ENTRYPOINT
, which allows you use mb
on the docker run
command.
An example is listed on the getting started page.defaultResponse
and endOfRequestResolver
is returned as part of the imposter configurationshellTransform
bug with long commandsMany thanks to the following kind folks for help with this release, either through bug reports, suggestions, or direct code contributions:
npm install -g mountebank@2.5.0
]]>
This release adds a significant amount of startup customization to mountebank.
configfile
CLI option or when saving test data using mb save
. See the new
formatter
CLI option for details.data
object to stringify
functions in the default
EJS formatter for the configfile
CLI optionlog
command line parameter.rcfile
command line parameter, allowing you to keep startup configuration in a JSON file.name
on the imposters page.shellTransform
behavior on Windows.copy
behavior to replace JSON keys as well as data.Many thanks to the following kind folks for help with this release, either through bug reports, suggestions, or direct code contributions:
npm install -g mountebank@2.4.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. |
*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:
npm
to install mountebank instead of the zip fileThis patch release resolves another security vulnerability unearthed by the amazing dcRUSTy.
--origin
CLI flag to pass in safe origins.numberOfRequests
is reset to 0 when sending a DELETE
request
to /imposters/:port/savedRequests
Many thanks to the following kind folks for help with this release, either through bug reports, suggestions, or direct code contributions:
npm install -g mountebank@2.3.3
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. |
*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:
npm
to install mountebank instead of the zip file