kurtosis-cli

Houses the kurtosis command line utility

Project maintained by kurtosis-tech Hosted on GitHub Pages — Theme by mattgraham

TBD

0.21.0

Breaking Changes

Upgraded to engine 1.26.1, core 1.54.1 and container-engine-lib 0.33.0
- Users will need to run kurtosis engine restart

Fixes

Fixed bug with Gateway erring out when getting service info for service with non TCP protocol port

0.20.1

Changes

Updated default kubernetes-enclave-data-volume-size to 1024Mb
Update to latest Kurtosis dependencies to switch to using EmptyDirs rather than PerstistentVolumeClaims

0.20.0

Breaking Changes

Upgraded to engine 1.25.4 and core 1.53.4
- Users will need to run kurtosis engine restart

0.19.2

Fixes

Revert “bugfix” from 0.19.1 that actually caused a bug

0.19.1

Features

Cluster config validation failures print out the name of the failed cluster

Fixes

Fix bug where enclave data volume size was getting force-overwritten if and only if it was set

0.19.0

Fixes

Fixes bugs that were happening with API container’s gRPC wire format
Fixes various bugs with files artifacts expansion
Fixed RemoveService in APIC gateway not killing local connection
Fixed APIC gateway trying to create a connection to a Kurtosis service with no ports specified

Breaking Changes

Upgraded to engine 1.25.3
- Users will need to run kurtosis engine restart

0.18.7

Changes

Upgraded to container-engine-lib 0.30.2, core 1.50.7, and engine 1.22.7

0.18.6

Changes

Upgraded to container-engine-lib 0.30.1, core 1.50.6, and engine 1.22.6

0.18.5

Changes

Upgraded to container-engine-lib 0.30.0, core 1.50.5, and engine 1.22.5

Features

kurtosis gateway now connects to user services running in cluster

Fixes

Fixed a bug where the gateway wasn’t rewriting user service requests with the local ports

0.18.4

Features

Added files artifact expansion in Kubernetes
Implemented copying files from a user service in Kubernetes

Changes

Increased the per-service availability-waiting time for the module test to 30s (but I suspect there’s some other weird nondeterminism going on)

0.18.3

Fixes

Upgrade to latest container-engine-lib, Core, and Engine which contain fixes for modules on Kubernetes
Switched module exec to the new Kurtosis command framework
Fixed the logs ReadClosers returned by service logs and module exec not getting closed

0.18.2

Fixes

Fix broken service logs command

Changes

Made it impossible to mess up the FlagType environment variable now when declaring new commands

0.18.1

Features

When the user adds a new config version, unit tests will now force (at compile time) the following:
- The user must add a new deserializer
- The user must add a new migration from the previous version
- The user must update KurtosisConfig to use the latest config struct

Fixes

Renamed the enclave-size-in-Megabytes -> enclave-size-in-megabytes tag on the Kubernetes config
Reverted a previous breaking change in config

0.18.0

Features

KurtosisClusterConfig now creates engine container config suppliers
Added a config version migration test
Connected the config file to use by the commands
Added tab-complete to the following commands:
- enclave dump
- enclave ls
- enclave rm
- service logs
- service shell
Added kurtosis cluster get|set|ls, which define which backend cluster (defined in config) that the CLI will access for all engine-related commands.
Added ‘gateway’ command to open a local gateway to kurtosis objects running in Kubernetes
Added calls to remote API container in API Container gateway
Added Kubernetes module CRUD & logs features

Changes

The enclave-size-in-Megabytes field in Kubernetes cluster field now is optional, and defaults to 10 MB
Upgrade to engine 1.21.4 which understands Kubernetes cluster definitions
Execution Ids now serialize timestamp as YYYY-MM-DDTHH-MM-SS-sss

Fixes

Fixed a bug where pods would return before being started
Upgraded to container-engine-lib 0.25.0 (and downstream deps), which fix several issues on Kubernetes
Bumped the number of retry polls in the module tests up to 20 to try and remediate a timeout while waiting for the datastore service to come up that we were seeing
Fixed the config getting serialized strangely
Fixed a bug where Kubrnetes service updates would sometimes fail

Breaking Changes

Upgraded to engine 1.22.0
- Users will need to run kurtosis engine restart to use the newest engine

0.17.0

Features

Added test_cli_functionality CircleCI test
Bump CircleCI resource class to large when building the CLI to speed build times
Added a build cache to the CLI build step

Changes

Upgraded to container-engine-lib 0.23.2, core 1.49.2, and engine 1.21.2 which use the new method of registering services

Breaking Changes

Upgraded the engine to version 1.21.0
- Users should run kurtosis engine restart after upgrading
CLI now requires Kubernetes enclave sizes to be specified in megabytes, not gigabytes
- Remediation: change all CLI yaml input parameters specifying enclave sizes in gigabytes to megabytes

0.16.3

Accidentally-released empty release; no changes

0.16.2

Features

Can use Kurtosis Core YAML config file format V1 to specify metrics preferences

0.16.1

Features

Can use kubernetes backend for engine commands through the --with-kubernetes flag
Upgraded to container-engine-lib which provides new (but still dormant) k8s functionality

0.16.0

Changes

Upgrade to engine 1.18.0, which uses the enclave data volume (rather than enclave data dirpath) for enclave data storage
enclave inspect no longer prints out the enclave data directory
- Users looking to explore an enclave’s data should now look for the volume with the enclave’s name, and mount that in a container
The module tests now use datastore-army image 0.2.2

Breaking Changes

The engine has now been upgraded to 1.18.0
- Users will need to run engine restart to get the new version of the engine

0.15.1

Features

Added service pause and service unpause to CLI
Added E2E tests for pause and unpause for both Golang and Typescript

Changes

Upgraded kurtosis core lib to 1.45.4 which adds EnclaveContext.PauseService and EnclaveContext.UnpauseService
Upgraded kurtosis engine lib to 1.17.4
Added uploadFiles tests for typescript and go clients.

Fixes

Fixed uploadFiles typescript test.

0.15.0

Features

Added files storeservice to store files from a service in the enclave
Updated files_artifact_mounting internal test in order to test duplicate mountpoints
Added a dedicated test for testing if files artifacts get mounted to the same location

Changes

Upgraded kurtosis core lib to 1.45.3 which adds EnclaveContext.StoreFilesFromService and removes EnclaveContext.RegisterFilesArtifacts
Upgraded kurtosis engine lib to 1.17.3

Breaking Changes

Upgraded the engine to v1.17.3
- Users should run kurtosis engine restart to use the latest version
- Users should upgrade their version of kurtosis-engine-api-lib to 1.17.3 as well
Removed several methods from EnclaveContext; users should follow the remediation steps here

0.14.1

Features

Added ContainerConfigBuilder.WithFiles which allows use of files artifacts uploaded via EnclaveContext.UploadFiles in services
Added files upload to send files into an enclave
Added a --files flag to service add to allow mounting files artifacts on the container
Added files storeweb to store files from a web URL in the enclave

0.14.0

Breaking Changes

Upgraded kurtosis engine lib to 1.15.0
- Users should upgrade to kurtosis-engine-api-lib 1.15.0

Changes

Replaced DockerManager with KurtosisBackend in module exec command
Upgraded container engine lib to 0.15.0

Features

Added destroy_enclave_test in Golang and Typescript internal testsuites
The old_enclave_continuity test now tests having stopped old enclaves around, as well as service add
Added an extra layer to the Docker exec command test to verify we’re not accidentally sh-wrapping the command
Many operations now happen in parallel in the backend, most notably making clean about 50-100% faster
Added a test to verify that kurtosis clean -a cleans up its containers, volumes, and networks

0.13.0

Features

enclave inspect now prints port IDs, in sorted order

Changes

Upgraded container engine lib to 0.14.3
Upgraded kurtosis core lib to 1.42.2
Replaced DockerManager with KurtosisBackend in:
- EngineConsumingKurtosisCommand struct and in RunFunc
- clean command
- enclave inspect command
- enclave rm command
- service logs command
- service shell command

Fixes

Fix a bug where Kurtosis would fail to process containers using the old port spec
Fixed a bug where enclave inspect crashes if a module is stopped

Breaking Changes

Upgraded kurtosis engine lib to 1.14.2
- Users should upgrade to kurtosis-engine-api-lib 1.14.2

0.12.2

Fixes

Bumping dependencies on:
- Engine Server 1.13.2
- Container Engine Lib 0.13.0
- Core 1.41.1

0.12.1 Breaking Changes

Bumped Dependencies for Kurtosis Core which is now version 1.41.0.
- Users using the ExecuteBulkCommands API should remove code referencing it.
- Additionally Enclaves should be restarted.
Bumped Dependencies for Kurtosis Engine Server which is now version 1.13.0.

0.12.0

Breaking Changes

Removed Repl and Sandbox commands because now CLI contains several tools to start enclaves, add user services and get access from outside on an easy way
- Users do not need to use Repl and Sandbox anymore, now the CLI contains commands to facilitate the creation of an enclave and running any kind of user service inside it

Changes

Upgraded the kurtosis core to 1.40.1
Upgraded the kurtosis engine to 1.12.0
Switched enclave dump to use KurtosisBackend

Fixes

Go testing now includes with CGO_ENABLED=0 variable so the user doesn’t have to specify environment variables before running scripts.

0.11.9

Features

Added the service add command for adding a service to an enclave
Added the service rm command for removing services from an enclave
Added an --id flag to enclave new to allow setting the new enclave’s ID
Users can now provide an existing enclave to the --enclave-id parameter of module exec to exec the module in an existing enclave, rather than creating a new one

0.11.8

Fixes

Fixed break in the sandbox command when we switched to the newer EnclaveContext.newGrpcNodeEnclaveContext function

0.11.7

Features

Upgraded container-engine-lib, core, and engine-server to allow for the new API container & enclave CRUD function stubs

Features

Updated engine_manager to use kurtosis_backend instead of docker_manager

0.11.6

Features

Bumped latest version of ‘object-schema-lib’, ‘kurtosis-core’ and ‘kurtosis-engine’
Code refactored according to the latest gRPC web feature

0.11.5

Features

Added a --with-partitioning flag to the sandbox command for turning on network partitioning

Changes

When a service doesn’t have any ports, <none> will be printed instead of emptystring to make it clearer that the service has no ports
Leave network partitioning off by default for the sandbox command

0.11.4

Features

Added a config path command to print the path to the Kurtosis config file
Added a --force flag to config init to allow users to ignore the interactive confirmation prompt (useful for running in CI)
If the user does end up trying to config init in a non-interactive shell when the config already exists, throw an error with informative information
Added CI checks to ensure that double-init’ing the config without force fails, and with force succeeds

Fixes

Fixed a bug with determining if the terminal is a TTY

0.11.3

Changes

Upgraded to the following, which contain dormant Kubernetes code:
- container-engine-lib 0.8.7
- core 1.39.3
- engine 1.11.1

0.11.2

Features

Detect if the CLI is running in non-interactive mode (i.e., in CI) and error if the InteractiveConfigInitializer is run
Add a test to verify that the CLI fails in non-interactive mode

0.11.1

Features

service shell will first try to find & use bash before dropping down to sh
Add a test to ensure that new versions of the CLI don’t break compatibility with enclaves started under an old version
Added a KurtosisCommand wrapper over the cobra.Command objects that we’re using to create CLI commands, so that we have a centralized place to add autocompletion
Added flags to KurtosisCommand
Added a NewEnclaveIDArg generator for building enclave ID args with tab-completion and validation out-of-the-box
Added tab-completion & enclave ID validation to enclave rm command
Added a EngineConsumingKurtosisCommand to make it easier to write commands that use the engine
Ported clean and config init to the new KurtosisCommand framework
Added a SetSelectionArg for easily creating arguments that choose from a set (with tab-complete, of course)

Changes

Switched enclave rm to use the new command framework
Switched enclave rm and enclave inspect to use the NewEnclaveIDArg component

Fixes

Made the error traces easier to read when enclave rm fails
Made the LowlevelKurtosisCommand unit tests less likely to experience false negatives

0.11.0

Fixes

Fixed several bugs that were causing product analytics events to get dropped for users who had opted in

Breaking Changes

Use engine version 1.11.0
- Users should upgrade to kurtosis-engine-api-lib 1.11.0

0.10.1

Fixes

Allow for 256-character labels

0.10.0

Breaking Changes

Upgraded to engine server 1.10.4, which makes name & label values compatible with Kubernetes
- Enclave IDs, service IDs, and module IDs must now conform to the regex ^[a-z0-9][-a-z0-9.]*[a-z0-9]$
The --kurtosis-log-level flag to set the API container’s log level has been renamed to --api-container-log-level for the following commands:
- enclave new
- module exec
- sandbox
The --kurtosis-log-level flag no longer exists for the enclave ls command
- Users should use --cli-log-level instead

Changes

The engine & API containers will log at debug level by default, to better help us debug issues that are hard to reproduce
Upgraded the engine server to 1.10.0
Upgraded the kurtosis core to 1.38.0
Upgraded the object-attributes-schema-lib to 0.7.0
Changed the generated kurtosis enclave name to lower case
Changed constants/vars in tests

Fixes

Fixed an issue where setupCLILogs was accidentally setting the logrus output to STDOUT rather than the Cobra command output
Removed several logrus.SetLevels that were overriding the CLI log level set using --cli-log-level
Fixed a bug where trying to destroy an enclave whose ID was a subset of another enclave ID would fail
CLI build.sh wasn’t calling go test
Fixed multiple log messages & stacktrace.Propagates that didn’t have formatstr variables
Fixed broken DuplicateFlagsCausePanic unit test

0.9.4

Features

Added the functionality to execute retries when sending user-metrics-consent-election fails

Changes

Upgraded the metrics library to 0.2.0

Fixes

Fix network_soft_partition_test in Golang and Typescript internal testsuite
Fix typo in metrics consent message

0.9.3

Fixes

Fix and error in CLI release version cache file generation

0.9.2

Fixes

Fixed a bug with engine restart using stacktrace.Propagate incorrectly
The yes/no prompt now displays valid options

Removals

On further review, removed the big long metrics paragraph from the config init helptext; this likely isn’t going to land well

Changes

Be more explicit in our explanation to users about product analytics metrics

0.9.1

Features

The enclave ID argument to enclave inspect is now tab-completable
Added a “Debugging User Issues” section to the README

Changes

Upgraded the engine server to 1.9.1
Upgraded the kurtosis core to 1.37.1
Upgraded the metrics library to 0.1.2
Switched the enclave inspect to the new command framework
Cleaned up our Kurtosis-custom logic wrapping the Cobra commands

Fixes

Fix the Kurtosis completion
The CLI version mismatch warning messages are printed to STDERR so as not to interfere with any other command output (e.g. completion)

0.9.0

Features

Added MetricsUserIDStore which generates a hashed user ID based on OS configuration, and saves the ID in a file to use it in future runs of the CLI
Pass two new arguments metricsUserdID and shouldSendMetrics to the EngineServerService.Launcher
Track if user consent sending metrics to improve the product

Breaking Changes

Required the user to make an election about whether to send product analytic metrics
- Users using Kurtosis in CI will need to initialize the configuration as part of their CI steps using these instructions
- Users will need to run kurtosis engine restart after upgrading to this version of the CLI
- Engine API users (e.g. in tests) will need to update to kurtosis-engine-api-lib 1.9.0

Changes

Upgraded the kurtosis core to 1.37.0

0.8.11

Features

The enclave ID argument to enclave inspect is now tab-completable

Fixes

Fix the Kurtosis completion

0.8.10

Features

enclave inspect now also prints the service ID in addition to the GUID
Add the -f flag to service logs to allow users to keep following logs

Fixes

enclave stop and enclave rm require at least one enclave ID
Turned down the parallelism of the Golang & Typescript testsuites to 2 (from 4), so that we’re less likely to face test timeouts (both on local machine & CI)

0.8.9

Fixes

Set the Typescript internal tests’ timeouts to 3m to match Golang
Fixed an issue where a failure to dump a container’s logs on enclave dump would incorrectly report that the issue was with a different container
Fixed enclave dump breaking if a REPL container is present

0.8.8

Features

Added TypeScript Tests to CI
Added configuration framework which is composed by:
- The KurtosisConfig object which contains Kurtosis CLI configurations encapsulated to avoid accidentally editions
- The KurtosisConfigStore which saves and get the KurtosisConfig content in/from the kurtosis-cli-config.yml file
- The KurtosisConfigInitializer handle KurtosisConfig initial status, request users if it is needed
- The KurtosisConfigProvider which is in charge of return the KurtosisConfig if it already exists and if it not requests user for initial configuration
- The config init command to initialize the KurtosisConfig, it requires one positional args to set if user accept or not to send metrics
Added PromptDisplayer to display CLI prompts
Added user metrics consent prompt to request user consents to collecting and sending metrics
Added override Kurtosis config confirmation prompt to request user for confirmation when they’re trying to initialize the config but it’s already created
Add enclave dump subcommand to dump all the logs & container specs for an enclave
After the internal testsuites run in CI, the enclaves are dumped and exported so Kurtosis devs can debug any test cases that fail in CI

Fixes

Limit the max number of Typescript tests running at once to 4, to not overwhelm Docker

Features

Added TypeScript test: network_soft_partition.test.ts
Added TypeScript test: network_partition.test.ts

Changes

When a module exec fails, don’t stop the enclave so the user can continue debugging

0.8.7

Features

Added TypeScript test: files.test.ts
Added TypeScript test: module.test.ts
Added TypeScript test: wait_for_endpoint_availability.test.ts
enclave inspect also reports the enclave data directory on the host machine

0.8.6

Features

Upgrade to engine server 1.8.2 which adds the removal of dangling folders in the clean endpoint

0.8.5

Features

Upgrade to engine server 1.8.1 which adds Kurtosis Engine checker in KurtosisContext creation

Features

Added TypeScript test: files_artifact_mounting.test.ts
Added TypeScript test: exec_command.test.ts

0.8.4

Features

The module exec command prints and follows the module’s logs

Changes

Upgraded to the following dependencies to support ID label:
- obj-attrs-schema-lib -> 0.6.0
- core dependencies -> 1.36.11
- engine dependencies -> 1.7.7

0.8.3

Features

Added call to clean endpoint

0.8.2

Fixes

Make a best-effort attempt to pull module & user service images before starting them
The headers of enclave inspect are printed in deterministic, sorted order so they stop jumping around on subsequent runs
Fix a bug where the sandbox would error on enclaveCtx.getServiceContext

0.8.1

Features

Added TypeScript test: bulk_command_execution.test.ts
Added TypeScript test: basic_datastore_and_api.test.ts

Fixes

Add proper logging for enclave_setup.ts
Fixed a bug with the Javascript REPL image
Resolve TypeScript test minor bug
Upgrade to engine server 1.7.3
Upgrade Typescript to the latest version of the engine-server library

0.8.0

Features

Upgraded to the following dependencies to support users specifying a user-friendly port ID for their ports:
- obj-attrs-schema-lib -> 0.5.0
- core dependencies -> 1.36.9
- engine dependencies -> 1.7.2
Added network_soft_partition_test in golang internal test suite
Added a unit test to ensure that an API break in the engine (which will require restarting the engine) is an API break for the CLI

Fixes

When the engine server API version that the CLI expects doesn’t match the running engine server’s API version, the user gets an error and is forced to restart their engine

Breaking Changes

Upgraded the engine server to 1.7.2
- Users will need to run kurtosis engine restart after upgrading to this version of the CLI
- Engine API users (e.g. in tests) will need to update to kurtosis-engine-api-lib 1.7.2
- Module users will need to update their modules to Module API Lib 0.12.3

0.7.4

Features

Added a --partitioning flag to module exec for enabling partitioning

Changes

The Go internal testsuite’s enclaves will now be named with Unix millis, rather than Unix seconds
Partitioning defaults to false for module exec

0.7.3

Features

Added new command named service shell (kurtosis service shell enclave_id service_id) which performs the same as docker exec -it container_id sh

0.7.2

Features

The enclave for module exec will now be named after the module image and the time it was ran
Allow users running module exec to manually specify the ID of the enclave that will be created

Fixes

Fixed a bug where service logs that was successful would really fail

0.7.1

Fixes

Attempt to fix CLI artifact publishing

0.7.0

Features

Added TypeScript: basic_datastore_test.ts, enclave_setup.ts and test_helpers.ts
Added TypeScript project inside of internal_testsuites folder.
The test_helpers class now has a higher-level API: AddDatastoreService and AddAPIService, which makes many of our internal testsuite test setups a one-liner
Add an extra API container status result to enclave inspect
Reimplement endpoint availability-waiting test in new Go test framework

Fixes

stacktrace.Propagate now panics when it gets a nil value
Fixed bug in files artifact mounting test where it would fail on Mac (but not Linux)
Fixed enclave inspect breaking if the enclave was stopped
Fixed publishing, which was temporarily broken

Changes

The Javascript REPL now uses Node 16.13.0 (up from 16.7.0)
Grouped all the internal testsuites into a single directory
Gave build.sh scripts to the CLI & internal testsuite subdirectories now
There is no longer a root go.mod, but now one in CLI and one in golang_internal_testsuite (rationale being that the dependencies for the CLI and for the internal testsuite are very different, plus we’ll have a typescript_internal_testsuite soon)
Removed the “local static” element to localStaticFilesTest, because there’s no longer a distinction between “local” and “static” now that the testsuite runs with Go test
The --image arg to engine start and engine restart has been replaced with a --version flag, so that the full org & image is no longer required
The --kurtosis-api-image flag to sandbox has been replaced with a --api-container-version flag, so that the full org & image is no longer required
The --api-container-image flag to enclave new has been replaced with a --api-container-version flag, so that the full org & image is no longer required
The --api-container-image flag to module exec has been replaced with a --api-container-version flag, so that the full org & image is no longer required
The engine status now returns the engine version, rather than the API version
Use engine-server 1.5.6
Remove all references to Palantir stacktrace

Removals

Removed the test command, as tests can be written directly in your testing framework of choice by connecting to the running engine using kurtosis-engine-api-lib
Removed the AdvancedNetworkTest, because we no longer have Network types
Removed alternating colors for the tables, because it’s a pain to maintain
Stop publishing a latest version of the REPL images, because the CLI should use pinned X.Y.Z version to avoid problems

Breaking Changes

Removed the test command
- Users should migrate their tests out of the Kurtosis testing framework, and into a testing framework of choice in their language
The --image arg to engine start and engine restart has been replaced with a --version flag
- Users should use the new flag with the Docker tag of the engine to start
The --kurtosis-api-image flag to sandbox has been replaced with a --api-container-version flag
- Users should use the new flag with the Docker tag of the API container to start
The --api-container-image flag to enclave new has been replaced with a --api-container-version flag
- Users should use the new flag with the Docker tag of the API container to start
The --api-container-image flag to module exec has been replaced with a --api-container-version flag
- Users should use the new flag with the Docker tag of the API container to start

0.6.8

Features

Added a cache file for getting the latest released CLI version from GitHUB API

0.6.7

Features

Added Yellow and White alternating colors in TablePrinter

Fixes

The kurtosis engine restart suggestion when the engine is out-of-date now:
- No longer has a trailing space
- Is on the same line as the “engine is out-of-date” message

0.6.6

Features

The API Container host port was added when showing the data with the command enclave inspect

0.6.5

Fixes

enclave inspect host port bindings now properly return 127.0.0.1, to match what’s returned by the AddService

0.6.4

Fixes

Fixed issue #69 - now the CLI version checker passes when the current version is newer than the latest public version (e.g. during a release)
Enable the unit test for the RootCmd because issue #69 is fixed

Changes

Removed version_checker class, now the checkCLILatestVersion functionality is part of the RootCmd and the checkIfEngineIsUpToDate functionality is controlled by the engine_existence_guarantor

0.6.3

Fixes

Temporarily disable the unit test for the RootCmd until issue #69 is fixed

0.6.2

Features

enclave inspect also prints the Kurtosis modules
Added version_checker.CheckLatestVersion method to check if it is running the latest CLI version before running any CLI command
Added version_checker.CheckIfEngineIsUpToDate method to check if it is running engine is up-to-date.

Fixes

Fixed error where service logs command is executed with a nonexistent enclave ID or nonexistent GUID just silently exits
Upgraded to engine server 0.5.2, which returns host port bindings in the format 127.0.0.1 rather than 0.0.0.0 for Windows users
Upped the run timeouts of the advanced network test, module test, and bulk command execution test to 90s

Changes

Replaced kurtosistech/example-microservices_datastore Docker image with kurtosistech/example-datastore-server in golang_internal_testsuite
Replaced kurtosistech/example-microservices_api Docker image with kurtosistech/example-api-server in golang_internal_testsuite
Replaced kurtosistech/example-microservices_datastore Docker image with docker/getting-started in bulk_command_execution_test and wait_for_endpoint_availability_test
Upgraded datastore army module Docker image to the latest version kurtosistech/datastore-army-module:0.1.5 in module_test

0.6.1

Fixes

Fixed a bug where a testsuite could be reported as passing, even when the tests were failing

0.6.0

Features

The engine loglevel can be configured with the new --log-level flag to engine start

Changes

Renamed the repl new image flag to make more sense
Update to using the engine server that stores engine/enclave data on the user’s local machine

Breaking Changes

The --js-repl-image flag of repl new has been renamed to --image, with shorthand -i

0.5.5

Fixes

A failed module exec or sandbox stops, rather than destroys, the enclave it created

0.5.4

Features

enclave new prints the new enclave’s ID
Information about how to stop or remove the enclave created by sandbox is printed after the REPL exits
Added a clean command, to clean up accumulated Kurtosis artifacts
Added a repl inspect command to list installed packages on the REPL

Fixes

Use --image flag in kurtosis engine start command, it was not being used when the engine is being executed
Fix the returning values order when DestroyEnclave method is called in kurtosis sandbox command
Fixed a bug where engine status wouldn’t check the error value from getting the engine status object
The Javascript REPL’s module installation paths in the Dockerfile are now filled from Go code constants (rather than being hardcoded)

Changes

The sandbox command no longer destroys the enclave after the REPL exits
Upgrade to engine server 0.4.7, where API container doesn’t shut down the containers after it exits (instead relying on the engine server to do that)

0.5.3

Fixes

Upgrade to the goreleaser-ci-image 0.1.1 to publish a new Homebrew formula with a fix for the bottle :unneeded deprecation warning

0.5.2

Features

Added enclave stop and enclave rm commands

0.5.1

Features

Add instructions for users on what to do if no Kurtosis engine is running
If an engine isn’t running, the CLI will try to start one automatically

0.5.0

Changes

Replaced EnclaveManager with Kurtosis Engine API Libs which handle all the interactions with the Kurtosis Engine Server

Features

Add a version command to print the CLI’s version, with a test
Added a global --cli-log-level flag that controls what level the CLI will log at

Fixes

The Kurtosis Client version used by the JS REPL image will now use the KurtosisApiVersion constant published by Kurt Client
Fixed bug where testsuite containers weren’t getting any labels

Breaking Changes

Interactions with the CLI now require a Kurtosis engine to be running
- Users should run kurtosis engine start to start an engine

0.4.3

Features

Added documentation in README about how to develop on this repo
Upgraded to kurtosis-core 1.25.2, which contains fixes for container-engine-lib 0.7.0 feature that allows binding container ports to specific host machine ports
Added engine start command to the CLI
Added engine stop command to the CLI
engine start waits until the engine is responding to gRPC requests before it reports the engine as up
Added engine status command to the CLI
Start a Kurtosis engine server in the CI environment

Fixes

Clarified the difference between the two types of params in module exec
engine start won’t start another container if one is already running
engine start waits for gRPC availability before it reports the engine up

0.4.2

Features

enclave commands also show enclave state
Standardized table-printing logic into a TablePrinter object
Added a KeyValuePrinter for pretty-printing key-value pairs
enclave inspect also prints the enclave ID & state

Fixes

module exec will attempt to update the module & API container images before running
Fixed a bug where having a node_modules directory in your current directory when starting a REPL will cause the REPL to fail

Changes

Upgrade to testsuite-api-lib 0.11.0, which uses Kurt Client 0.19.0 (already handled in v0.4.0 of this repo)
When running a REPL, your current directory is now mounted at /local rather than the present directory

0.4.1

Fixes

Update the Javascript CLI’s core-api-lib version to 0.19.0, to match the rest of the code

0.4.0

Changes

Switched all references to “Lambda” to “module”

Fixes

ModuleTest (renamed from LambdaTest) now uses the ports returned by the Datastore Army module
Fixed bug in CI where pipefail wasn’t set which would result in the testsuite-running step passing when it shouldn’t

Breaking Changes

Renamed the lambda command to module

0.3.4

Fixes

Stop attempting to upload APK packages to Gemfury (which can’t accept APK packages and throws an error)

0.3.3

Features

Added a repl install command for installing NPM packages to a running REPL container
ParsePositionalArgs (renamed to ParsePositionalArgsAndRejectEmptyStrings) now also errors on empty strings

0.3.2

Features

Added enclave new command to create a new enclave
Added repl new command to start a new Javascript REPL
Added REPL runner to reuse the creation and execution of the REPL container
Print interactive REPLs in enclave inspect
Added GetEnclave method in EnclaveManager in order to get information of a running enclave
Upgrade Kurtosis Core Engine Libs to v0.6.0 which adds Network type
Upgrade Kurtosis Core to v1.24.0 which splits api-container-url into api-container-ip and api-container-port

0.3.1

Fixes

Pinned the default API container version to the same version as in the go.mod, so that its version can’t silently upgrade under users and break everything

0.3.0

Changes

Changed the Homebrew/deb/rpm package name to kurtosis-cli (was kurtosis)

Breaking Changes

The CLI is now installed via the kurtosis-cli package (for Homebrew, APT, and Yum) rather than just kurtosis