SH-965: AWS: Form should not filter out EIP currently assigned.SH-959: Users: It should be possible to save users without any permissions.SH-958: Maven Repositories: Concurrent downloads crash.SH-957: Users: Team admins should be able to remove users from their team.SH-956: Authentication: Invalid cookies shouldn’t spam logs.SH-969: Docker: Introduce certified images for ARM.SH-961: AWS/Azure/GCP/Docker: Introduce “latest” certified images with the latest to date Java version (20 as of now).Please check the full release note for more details. Otherwise, you need to change the ownership of your private key files (mounted to /opt/frontline/keys in the container): chown 1001:0.If you run Gatling Enterprise on OpenShift with the default user settings, you have nothing to do (OpenShift already overrides the user by default).by using the user key in Docker Compose, or the runAsUser directive in Kubernetes), you have nothing to do. If you already explicitly override the user (e.g.This is because the default user for the gatlingcorp/frontline container is no longer the root user (it now defaults to the uid:gid 1001:0). If you run the Gatling Enterprise server in Docker (including Kubernetes) with the default user: you will need to change the owner of your private key files. SH-972: Authentication: Store default permission on first OIDC connection.SH-977: AWS/Azure/GCP/Kubernetes: Let users define a JAVA_HOME env var for the load generators.SH-975: AWS: Enforce IDMSv2 on-demand AWS load generators.SH-201: On premises: Block adding a username in the hostname.Please check the full release note for 3.9.4 and for 3.9.5 for more details. SH-979: AWS/Azure/GCP/Kubernetes: Fix regression introduced by SH-977 in 1.18.4.SH-980: Kubernetes: Introduce option (default true) to be able to honor the default kubeconfig file.1.18.5 () # Gatling Enterprise # Features #
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |