Fix AWS perf tests for Thunder v0.48.0 - #67
Merged
Merged
Conversation
UdeshAthukorala
changed the title
rajithacharith
approved these changes
Jul 16, 2026
ThumulaPerera
approved these changes
Jul 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Purpose
Thunder v0.48.0 broke the AWS perf suite in two ways, both showing up as
100.00% errors.thunder-id/thunderid#3779 added an
operationdatabase and made the SSO session service initialise at startup. Ourdeployment.yamlonly definesconfig,runtimeanduser, so v0.48.0 exits withfailed to get operation database client: database type is not configuredand never binds a port. Seeding failed because Thunder was down, so the harness reporting "management APIs rejected the requests (401/403)" is misleading. (run #29312371882)thunder-id/thunderid#3762 gates
/auth/**behindserver.security.direct_auth_secret, soAuthenticate_With_Credentials.jmxwas rejected at the security middleware on every request (191,993 samples, ~40ms each).setup.shgenerates a random secret per run when none is configured, but honours a pinned one. (run #29396473094)Changes
create_database.sql: createoperationdband load its schema.deployment.yaml: add theoperationstanza, and pinserver.security.direct_auth_secret.perf-test-thunder.sh: new-aoption, passed to the scenarios as-JdirectAuthSecret.Authenticate_With_Credentials.jmx: send theDirect-Auth-Secretheader.