Releases: mockoon/cli
v1.6.0
This release adds support for Mockoon v1.18.0.
OpenAPI support
The CLI is now compatible with OpenAPI specification files v2.0.0 and 3.0.0 (both JSON and YAML). To directly mock an OpenAPI specification file, simply run the start
command by providing the URL or a local path to a specification file:
$ mockoon-cli start --data ~/path/to/your-opeanapi-file.yaml
(Issue #18)
Run multiple mocks at once
Running multiple mocks at once is now possible by providing multiple paths or URLs to the --data
flag. This is compatible with both managed processes and foreground processes. --data
, --pname
, --port
and --hostname
flags can receive multiple values to run and configure multiple mocks:
mockoon-cli start --data ./mock1.json ./mock2.json --port 3000 3001 --pname mock1 mock2 --hostname 127.0.0.1 192.168.1.1
The dockerize
command now also supports copying multiple mocks and exposing multiple ports.
(Issue #57)
Legacy exports deprecation and removal
Since legacy Mockoon's export format was removed in the application's latest version, --all
, --index
and --name
flags were removed from the CLI. Though, the CLI is still able to run mocks from an old export file.
Running multiple mocks can now be achieved thanks to the above method.
v1.5.1
v1.5.0
Features
- Logs are now sent to both stdout (console) and files when using the provided Docker image. (Issue #33)
Fixes
- Data file is now copied correctly next to the generated Dockerfile when using the
dockerize
command with--output filename
(no path). (Issue #53) - Increased download timeout to 30 seconds when loading a data file from a URL.
v1.4.0
Features
- A new
--log-transaction
flag is available to log the full HTTP transaction. If enabled, the logs will contain the same information that can be found in the application. (Issue #34) - The CLI can now be run in the foreground as a blocking process with the
--daemon-off
flag. In this case, logs are both directed to stdout (console) and the usual files. (Issue #43)
Improvements
- A new
--repair
flag can be used to automate running mocks with old file versions (CLI won't prompt about migrating/repairing the file anymore). (Issue #50)
Fixes
- The CLI is not crashing anymore if environment's name contains slashes or backslashes. (Issue #42)
v1.3.0
v1.2.1
Improvements
- Add the API prefix in the
list
command output (Issue #45):
Name Id Status Cpu Memory Hostname Port API prefix
───────────── ──── ───────── ────── ───────── ────────────── ────── ────────────────────────
mockoon-test 0 online 0 54.7 MB 0.0.0.0 3000 salut
Thank you
A big thank you to the following people that helped to make Mockoon CLI better:
- @saravanan30erd: API prefix in the
list
command details. (Issue #45)
V1.2.0
This release adds support for Mockoon v1.16.0.
Features
-
Following Mockoon's changes in version 1.16.0 the CLI is now directly compatible with Mockoon's environment files, without the need to use the export method. You can read more about this in our blog post. (Issue #38)
-
Like the main application, the CLI now resolves body files relatively to the environment or export file location. (Issue #37)
Improvements
- We added an environment schema validation to ensure that the environment you load is valid. This system is able to repair environment files should they miss any property. This is especially useful when environment files were created manually. (Issue #39)
v1.1.0
This release adds support for Mockoon v1.15.0.
Features
- Add a new
hostname
flag that allows users to specify the hostname on which to listen at runtime (Issue #30). Also add support for localhost only hostname. (Issue mockoon/mockoon#469)
Improvements
- Update the message when a data file has the wrong format. (Issue #35)
v1.0.1
v1.0.0
Mockoon CLI is out of beta! 🎉 Thanks to all the members of our community who helped improve it.
This release adds support for Mockoon v1.14.0 new features and improvements.
Breaking changes
- We dropped support for Node.js v10 as its maintenance window is ending.