Skip to content

1.0.0 - Release Highlights

⚠️ Breaking change: Docker image registry change

From v1.0.0, Galasa Docker images are published to icr.io/galasa instead of icr.io/galasadev.

To give users time to migrate, images will continue to be published to icr.io/galasadev for a number of releases after v1.0.0. However, you are encouraged to update any references to icr.io/galasadev as soon as possible, as publishing to that registry will stop in a future release.

If you have any automation that pulls Galasa images directly — for example, custom Helm values.yaml overrides, CI/CD pipelines, scripts, or docker pull commands referencing icr.io/galasadev — you should update those references to use icr.io/galasa.

For example, if you currently reference: 

icr.io/galasadev/galasa-boot-embedded-amd64:0.48.1
update this to: 
icr.io/galasa/galasa-boot-embedded-amd64:1.0.0

See Upgrading to v1.0.0 for more details.

Changes affecting the Galasa Service

  • A new Opaque credential type is now supported in the Galasa Credentials Store. Opaque secrets store arbitrary opaque data (for example, licence JAR files such as my_license.jar) that tests can retrieve at runtime via the Credentials Store. The galasactl secrets set command gains two new flags: --secret-file (reads a file from disk and base64-encodes its contents) and --base64-secret (accepts an already-encoded string). Opaque secrets are mutually exclusive with all other credential fields. The REST API PUT /secrets/{name} and GET /secrets/{name} endpoints support the new Opaque type alongside the existing types.
  • galasactl secrets set now accepts an empty string ("") as the --password when creating or updating a KeyStore secret, to indicate a keystore with no integrity-check password. When updating an existing KeyStore secret, the keystore and keystorePassword fields must now be provided together to validate the KeyStore and its password.

Changes affecting tests running locally

  • Windows Credential Manager support added to the OS Credentials Store extension. Galasa can now securely read test credentials from Windows Credential Manager, providing a more secure alternative to storing credentials in plain text configuration files. See Windows Credential Manager Store for more details.

  • JMeter Manager now supports LOCAL execution mode using pre-installed external JMeter binaries, eliminating Docker dependency for performance testing.

  • Fixed an issue where multiple Galasa test classes could not be run in one galasactl runs submit local command. You can now supply multiple --class flags to run multiple test classes sequentially.

  • Added --offline flag to galasactl runs submit local. When set, the test JVM does not contact any remote Maven repositories — all required bundles must already be present in the local Maven cache. The flag is mutually exclusive with --remoteMaven.
  • Added new galasactl runs prepare local command. This pre-fetches all OBR bundle dependencies to the local Maven repository without running tests, enabling fully offline test execution on a subsequent galasactl runs submit local --offline invocation.