${GALASA_HOME}/bootstrap.properties file using the maven.repository.username and maven.repository.password properties. Alternatively, credentials can be supplied as environment variables by setting GALASA_MAVEN_USERNAME and GALASA_MAVEN_PASSWORD. Values in environment variables take precedence over values in the bootstrap.properties file.secretName field that contains the name of an existing Galasa secret containing the credentials to use when authenticating with Maven repositories. The secret name can be set using the galasactl streams set --name <stream-name> --maven-secret-name <secret-name> command or via YAML files with the galasactl resources apply command (see Test Streams as GalasaStream resources for more details).service.tokens.lifespan.nearly.expired.warning.days (min: 1 day, max: 30 days).galasactl auth tokens get command displays token expiry dates.For more information, see Configuring authentication.
Added a background cleanup process for the Galasa service's result archive store which automatically deletes test runs that meet the configured criteria.
For information on how to configure the cleanup process, including how to adjust the age threshold, cleanup frequency, and exclude specific test runs from cleanup, see Configuring automatic cleanup of test runs.
Added support for integrating the Galasa service with the Istio service mesh.
For configuration details, see Installing an Ecosystem using Helm.
User operations are now case-insensitive. All user-related operations in the Galasa ecosystem now treat user login IDs case-insensitively. This means that myuser, MyUser, and MYUSER are all treated as the same user. Users no longer need to remember the exact case a user was saved into the Auth Store with when passing the value manually or from an automation tool, which would previously cause user not found errors. This improvement applies to:
galasactl users get/set/delete --login-id, galasactl auth tokens get --user, and galasactl runs submit --user/users and /auth/tokens query parametersTest run submissions: The user field in test run requests
Added support for creating/updating Java keystore secrets (JKS and PKCS12 formats) in the Galasa Service's credentials store using galasactl secrets set. For more information, see the command reference.
The artifacts.properties file containing information about a local test run's artifacts will no longer be created and stored in the local RAS. Instead, an artifacts.json file will be created to provide more flexibility in the amount of metadata that can be included for each artifact. artifacts.json was already provided for runs in a Galasa service so the artifacts.properties file will simply no longer be provided.
Kubernetes Manager improvements: The Kubernetes Manager is now functional after several bug fixes. Credentials are now optional when using kubectl proxy (localhost:8001) for simplified local testing with Minikube. The manager also includes comprehensive documentation for both local and remote cluster setup, including SSL certificate troubleshooting.
framework.test.run.timeout.minutes that can be used to configure the maximum amount of time that a test can run for before being interrupted and assigned the 'Hung' result. See #2551.Added support for storing Java KeyStore credentials in the Galasa Credentials Store, enabling secure storage of SSL/TLS certificates and private keys. KeyStore credentials can be managed via the Secrets REST API using the new KeyStore secret type, which accepts PKCS12 or JKS format keystores encoded in base64. This feature allows managers like the Docker Manager to authenticate to services that require client certificates, such as Docker engines with TLS-protected daemon sockets. The KeyStore data, password, and type are validated during credential creation to ensure immediate feedback on invalid configurations. See #2509.
HTTP Client Manager: Upgraded the underlying HTTP client library from Apache HttpClient 4 to Apache HttpClient 5.
The existing getFile() methods that return CloseableHttpResponse are now deprecated but remain functional for backward compatibility. Users are encouraged to migrate to the new getFileStream() methods. See the HTTP Client Manager documentation for examples.
The galasactl runs submit local command now allows additional --obr flags to be supplied alongside a --gherkin flag. See #2562.
Added new REST API endpoints POST /streams and PUT /streams/<streamName> to allow users to create and update test streams. See the REST API reference for more details. See also #2447.
Added a new galasactl streams set command that can be used to create or update test streams within a Galasa service. See the command reference.
Added support for Gateway API for accessing the Galasa service. See Installing an Ecosystem using Helm for details on how to configure Gateway API. Ingress is still used for accessing the Galasa service by default but can be replaced with Gateway API by setting the ingress.enabled value to false and the gatewayApi.enabled value to true in the values.yaml file used when installing the Helm chart.
galasa-user skill from the Galasa repository and configure your AI-powered development environment to use it.includeCursor query parameter has been marked as deprecated in the Galasa Service's GET /ras/runs REST API endpoint as cursor-based pagination is now enabled by default. This query parameter should be removed from requests to this endpoint.rsa-sha2-256 and rsa-sha2-512. See #2461.@ZosProgram annotation are uppercase and no longer than 8 characters. If a name is not uppercase or exceeds eight characters, the z/OS Program Manager rejects it and raises a ZosProgramManagerException with an actionable error message.priority modifier associated with them that can affect the order in which tests submitted by users are scheduled. Tests submitted by users with higher priority modifiers can be scheduled before tests that were submitted by users with lower priority modifiers. See #2176.User priorities can be updated using the new --priority flag in the galasactl users set command. See the command reference.
Administrators can now set a user to associate with a batch of test runs when they are submitted, which may or may not be the same as the requestor. This allows admins who run batches of tests in an automation tool or workflow where the requestor is a functional ID/bot account, to also associate a user with the test runs, so these runs can be queried by the user later.
--user flag on the galasactl runs submit command. See the command reference.Runs can now be queried by user in the galasactl runs get command with the --user flag. This will return any runs where the user or requestor matches the value passed in with the --user flag. See the command reference.
Added galasactl tags commands to the Galasa CLI tool that can be used to create, read, update, and delete test tags as resources on the Galasa service. See the command reference for more details.
priority modifier that can affect the order in which tests submitted to a Galasa service are scheduled. Test submitted with tags that have higher priority modifiers will be scheduled before tests that have no tags or tags with lower priority modifiers. Tags can also be assigned a description which can be used to provide more information about the tag.
galasactl runs submit local commands can now be supplied with one or more --methods flags to run a selection of test methods locally from a Galasa test class that is provided with the --class flag. See the command reference for more details.
framework.resource.management.local.queued.timeout CPS property to the desired amount of time in seconds.galasactl runs cleanup local command which runs resource management providers (Java classes implementing Galasa's IResourceManagementProvider interface) to clean up resources. See the new command syntax.If your Kubernetes cluster is at version 1.34, we recommend upgrading to Galasa 0.44.0 to avoid issues with scheduling test pods onto the cluster.
The Galasa service Helm chart's eventStreamsSecretName value is now optional and a value is no longer provided by default.
The image used by Galasa in init containers, which contains the kubectl tool has been replaced.
bitnami/kubectl image was used by default to make some pods wait for others to start, to avoid an error storm which would happen if all the pods started up at the same time. This enforces an ordering of pods starting up which matches their dependencies.bitnami images were withdrawn, so the default value in the helm values.yaml file was switched to use a different image containing the same tool: kubectlImage: "rancher/kubectl:v1.33.5"Previous releases are also effected, so administrators of older installs of the Galasa service will also need to make this change and update their helm install.
Added log4j2Properties and log4jJsonTemplatesConfigMapName configuration settings in the Galasa service Helm chart to allow users to configure Log4j in their Galasa service. See the Installing an Ecosystem using Helm documentation for detailed instructions on how to do this.
Added a configuration setting couchdb.documentRevisionLimit in the Galasa Helm chart to control the maximum number of document revisions that should be stored in the CouchDB service. See #2439.
Deprecated the callback_url query parameter in the Galasa REST API's GET /auth endpoint in favour of a new base64_callback_url query parameter, which takes a Base64URL-encoded URL that the API will redirect back to after authenticating. See #2416.
Added a configuration setting certificatesConfigMapName in the Galasa service Helm chart to allow users to supply public certificates for Galasa service pods to use. See the Installing an Ecosystem using Helm documentation for detailed instructions on how to do this.
Galasa no longer supports Java 11. Galasa tests must be run with a Java version 17 JDK.
The 3270 manager's ITerminal interface has a new toJsonString() method that allows tests to convert the current 3270 terminal screen into JSON format.
The VTP manager has been removed from the available Galasa managers as the IBM Z Virtual Test Platform offering has been discontinued. See #2460.
The Galasa service now creates a test run record in the Result Archive Store when each run is submitted, rather than when the test is scheduled to execute, so more test runs will appear in the 'queued' state awaiting execution now. This also allows observability of submitted runs which were cancelled prior to being scheduled, which was not previously possible.
The Galasa service has been made more efficient by reducing the amount of data being exchanged between internal components and avoiding the exchange of large messages travelling over the gRPC protocol. See #2312.
Upgrades are handled better: The Galasa Helm chart creates the _users database in CouchDB if it doesn't already exist. This is a required database for CouchDB that should be created as default to prevent errors when the Result Archive Store is started. This is needed because latest version of CouchDB needs this database, and it may not have existed before.
The Galasa service is more robust when failures occur: A deployed Galasa service will now only attempt to launch tests in a new Kubernetes pod if the ETCD and RAS services are working. Were either of the ETCD or RAS services to fail, the errors would not be compounded by launching more tests which would all fail anyway.
Cancelling test runs which have not already finished is handled better: Running tests are given an opportunity to notice they have been cancelled, and to exit cleanly after releasing any resources they hold. Queued test runs are marked as cancelled immediately.#2317.
Java API enhancement: Updates have been made to the @TestResultProvider annotation. The @TestResultProvider can now provide a list of ITestMethodResults to the test which each include the method name, if the method passed, if the method failed, and the exception thrown to cause the failure, if available. This can be used by tests themselves to determine actions to take based on each method's result. See issue #2343.
The start and end line number in the run log pertaining to a particular method are now available in the test structure. This can be used to navigate the run log and identify which sections of the run log are about which methods. See issue #2214.
z/OS telnet 3270 server certificates can now be verified if the CPS property zos.image.[TAG].telnet.tls.verify is set to true. See issue #2296.
Galasa users without internet access can continue to read the Galasa documentation offline. The Galasa zipped distribution, isolated.zip, now contains a docs.tar file that when untarred becomes a Docker image. This Docker image can then be run to access the Galasa documentation site from a local web server.
log4j-core dependency upgraded from 2.24.1 to 2.25.1 to remediate a Critical vulnerability.
The Galasa documentation site now complies with EEC regulations, providing a privacy statement and standard cookie consent banner.
Cancel a run group using the Group ID. See the new command syntax
For developers of Galasa: Easier development of the Web user interface
Added a configuration setting kubeLaunchIntervalMillisecs in the Galasa Helm chart to control the time between launching of successive test runs, to space out launches more evenly so that Kubernetes is not as stressed.
Various defects, fixes, version uplifts
Make contributing code easier:
galasa repository.
This simplifies the build process for the Galasa documentation and makes changes on a git fork easier to build and verify.
It also facilitates closer integration between the javadoc, REST interface, CLI syntax and the rest of the material.New look for the Galasa web site: