- Dependency updates
- Switch to npm trusted publishing
- Switch to npm trusted publishing
- Dependency updates
- Dependency updates
- Dependency updates
- Dependency updates
- Add
--retriesand--retryIntervaloptions toexperiment runcommand to retry on validation errors (e.g., missing targets)
- Dependency updates
- Dependency updates
- Dependency updates
- Dependency updates
- Dependency updates
- Dependency updates
- Dependency updates
- Dependency updates
- Dependency updates
- Dependency updates
- Dependency updates
- add --verbose option for request logging
- Dependency updates
- Dependency updates
- add option --allowParallel to run an experiment in parallel to other experiments. e.g.
steadybit experiment run -k ADM-1 --allowParallel --yes
- add param forcePersist=true to run an experiment to create always an execution
- feat: allow parallel experiment executions
advice validate-status- parameterqueryis now optional- Execution of experiments will now show a link to the ui.
- Removed unnecessary dependency
- Update base image to node 22 / npm 11 (CVE-2024-21538)
- Dependency updates
- Dependency updates (CVE-2024-21538)
- Dependency updates
- Requires Node >= 18
- Renamed
experiment get-alltoexperiment dumpto prevent misuse. - Added
advice validate-status
- Dependency updates
- Add get-all command to fetch all experiments
- Experiment execution shows error/failure reason
- Fixed experiment execution via key / file
- Added support to configure profiles non-interactively
- Breaking: Policies feature has been removed from CLI and is not longer supported
- New
experiment [get|apply|delete]commands - New
experiment run -f <file>to execute experiment from file
- Upgrade Node.js version in CLI Docker image to avoid high severity security issues.
- Support new exit state
ERROREDof experiments
- Use new team api format
- Breaking: This version contains breaking changes within the CLI interface. All commands previously found
under
steadybit serviceandsteadybit service-definitioncan now be found understeadybit policy-binding. This was done to remove the problematic termserviceandservice-definition. - Update the Node.js version to Node.js 18 within the Docker image.
- Adding a new service will yield the services
idso the API server can figure out a proper one.
- Adding
http-client-fault-tolerancepolicy to the list of available policies when runningsteadybit service init.
- Changed
execandexecutetorunin all descriptions and commands to align the cli to the platforms wording. Added an aliasexecfor backward compatibility.
- Publish Docker image additionally under the major version, e.g.,
steadybit/cli:2
- Add missing
gitdependency to the CLI Docker image.
- Maintenance release to retag the Docker image.
steadybit experiment execcan be used to execute single experiments.
- initial version of the CLI Docker image.
- Correct license file header.
- Execute tasks via
steadybit service exec.
- Added a confirmation dialog if the user did not select any policies.
- Improve first-user experience when using the CLI.
- Fail hard when an incompatible Node.js version is used.
- Upgrade versions of policies suggested via
steadybit service initto0.2.2. - Provide additional help when a conflict occurs while running
steadybit service apply.
steadybit config profile addnow provides guidance w.r.t. the API access token creation.
steadybit service initnow has an improved policy selection process.
- Node.js v14 support.
steadybit service initgives more meaningful error messages in case the Steadybit servers fails to respond successfully with teams.- The service definition file name may now be supplied via the
-foption. By default, all commands assume that the default service definition file name is.steadybit.yml. - Print a success message when a service definition was applied.
- Change label from
pendingtonot checkedinsteadybit service verifyoutput. steadybit def-repo set-versioncan be used to modify version numbers in a task and policy definition repository.steadybit def-repo checkcan be used to check task and policy definition files in a repository for format, consistency and references.
steadybit service lsrenamed tosteadybit service show
steadybit service lscan be used to get a (filtered) list of policies and tasks.
steadybit service verifynow correctly terminates with status code1when at least one task is either pending or failing.
- Breaking: The service definition yaml format was changed to directly specify policies and tasks instead of desired resilience levels.
- Breaking: Health definition subsection was removed service definitions.
- Breaking: Adapted the
steadybit service verifybehavior so that it is compatible with the reworked API model. steadybit service applynow helps to resolve conflicts.steadybit service initnow asks for team and environment information.steadybit service applynow attaches auto-generated tags to the service definition which provide information about the repository, commit and ref.
- First public release.
steadybit service verifyexit code is wrong.
- List succeeded/failed/pending tasks in
steadybit service verifyoutput.
- Change terminology in
steadybit service initcommand to comply with terminology found in the public documentation. - Add a
steadybit service verify .steadybit.ymlcommand to compare the actual vs. desired resilience level.
- Correct supported Node.js version to
>=16. - Send a
User-Agentheader when making Steadybit API calls. - Add a
steadybit service open .steadybit.ymlcommand. - Add the ability to manage configuration profiles via
steadybit config profile.
- Rename
contracttoservice definition - Support a
deletecommand. - Rename
establishtoapplyto be closer to the wording of kubectl. - Add
steadybit serviceas an alias forsteadybit service-definition. - Engines field defines unsupported Node.js version. Node.js >=14.17.0 is required because of our
AbortControllerusage. - Define correct
Content-Typeheader when making API calls with request bodies.
- Add validation to the
contract initcommand. - Adapt generated yaml structure to new format.
- Improve documentation.
- Initial release for internal testing