Could specify the Keycloak version that can be used

[mablds]

Describe the bug

It's not a Bug itself. This is more a request from a person who lost a good time trying to configure this with the Keycloak latest version haha. If it is on the wrong place, just say to me that a move this issue/suggestion.

I understood that your main branch is where you're working on the next release that is aiming to run on 16.1.0 keycloak version. And the last release published is aiming to 15.0.2. But just after some hours I could understand this flow after look and compare the pom.xml files on main and on the Source Code from keycloak-benchmark-0.6 release.

My suggestion is to specify on release notes the Keycloak version that can run it.

[pgbezerra]

I couldn’t agree more, @mablds. Maybe release a package for, I don’t know, the last 3 keycloak versions

[ahus1]

Thanks for bringing this up. At the moment this project is more a toolbox to pick and adapt. Documentation and an accompanying test set to show which version works is lacking.

Once there's an automatic provisioning for the different scenarios and a minimal GitHub actions run, I'll be more confident to put such a statement at the front of the project.

Any helping hand on the way there is welcome, for example a shell script (?) that prepares a Keycloak instance with a matching Gatling service account (or whatever configuration the scenario needs).