v0.4.2

k6exec v0.4.2 is here 🎉!

What's Changed

The most important enhancement is the use of the new archive analysis introduced in k6deps v0.2.4 that does not require extracting the archive's content to disk.

Enhancements

add debug logs by @pablochacin in #104
use new k6 config location by @pablochacin in #119

Chores

build(deps): bump github.com/grafana/k6deps from 0.2.1 to 0.2.2 by @dependabot in #107
update k6provider v0.1.10 by @pablochacin in #105
build(deps): bump github.com/spf13/cobra from 1.8.1 to 1.9.1 by @dependabot in #110
update test archive by @pablochacin in #118
update dependencies by @pablochacin in #120
Full Changelog: v0.4.1...v0.4.2

v0.4.1

Changelog

Enhancements

• always display error before exit (#102)
• use k6 cloud credentials (#98)

Fixes

• fix-default-build-service-url (#101)

Chores

• build(deps): bump github.com/grafana/k6deps from 0.2.0 to 0.2.1 (#95)
• build(deps): bump golang.org/x/term from 0.28.0 to 0.29.0 (#96)

v0.4.0

Changelog

k6exec now uses k6provider

k6exec now uses k6provider to get the k6 binary with the required extensions.

k6provider offers configuration options via environment variables that are honored by k6exec.

• K6_BUILD_SERVICE_AUTH: authentication token to access the build service.
• K6_DOWNLOAD_AUTH: authentication token used to download binaries.

Breaking changes

k6provider library only supports getting binaries from a k6build service. Running a local build is not longer supported.

Therefore providing a the URL to this service is required. It can be provided using either the K6_BUILD_SERVICE_URL environment variable or the --build-service-url CLI option.

Known issues

• The binary is no longer automatically cleanup after execution k6exec#91
• Concurrent executions sharing can fail due to a conflict downloading the binary k6provider#43

k6exec supports k6 cloud command

k6exec now supports running the k6 cloud command.

v0.3.0

k6exec v0.3.0 is here 🎉!

Embedded k6 PoC removed

The embedded k6 PoC introduced in v0.3.0 does not allow k6exec to be installed using the regular go install command. Since we want to keep the go install installation method, the embedded k6 PoC has been removed.

Description from the v0.2.0 release notes:

Default k6 executable has been embedded

For a better user experience, the default k6 executable has been embedded in k6exec. If the user does not use any extensions and does not specify any version constraints for k6, the embedded default k6 executable will be executed. This results in much faster execution in a significant number of cases.

v0.2.0

k6exec v0.2.0 is here 🎉!

Default k6 executable has been embedded

For a better user experience, the default k6 executable has been embedded in k6exec. If the user does not use any extensions and does not specify any version constraints for k6, the embedded default k6 executable will be executed. This results in much faster execution in a significant number of cases.

Dependency updates

• grafana/k6deps updated to v0.2.0
• k6 provisioning logic extracted to grafana/k6provision v0.1.0

v0.1.12

k6exec v0.1.12 is here 🎉!

This release includes dependency updates:

• k6build to v0.5.0

v0.1.11

k6exec v0.1.11 is here 🎉!

This release includes dependency updates:

• k6deps to v0.1.8
  • fix semvers with build metadata are unmarshalled incorrectly
  • If the version is v0.0.0, then support for build metadata in version constraints according to semver

v0.1.10

k6exec v0.1.10 is here 🎉!

This release includes dependency updates:

• k6build to v0.3.5
• k6deps to v0.1.7
• k6pack to v0.2.3

v0.1.9

k6exec v0.1.9 is here 🎉!

This release includes:

• Update k6deps to v0.1.6: Support import path of arbitrary depth (deeper than three levels) (eg k6/x/foo/bar). Drivers of the xk6-sql extension use 5-level deep imports (eg k6/x/sql/driver/ramsql)

v0.1.8

k6exec v0.1.8 is here 🎉!

This is an internal bugfix release.

Fix subcommand flags handling

Passing subcommand specific flags was not possible, k6exec swallowed these flags.
This has been fixed.