Add Containerization To Load Test #1130
Conversation
Co-authored-by: James Herr<[email protected]>
…nerating and linking placer order id, replaced in message
…CDCgov/trusted-intermediary into story/1121/dockerize-load-tests
…CDCgov/trusted-intermediary into story/1121/dockerize-load-tests
Bring back silence
Co-Authored-by: Luis Pabon<[email protected]>
…CDCgov/trusted-intermediary into story/1121/dockerize-load-tests
docker-load-execute.sh
Outdated
| warm_up_api() { | ||
| echo 'Warming up API...' | ||
| pem=$(pwd)/mock_credentials/organization-trusted-intermediary-private-key-local.pem | ||
| token=$(jwt encode --exp='+5min' --jti $(uuidgen) --alg RS256 --no-iat -S@${pem}) |
There was a problem hiding this comment.
You could read the JWT from the mock_credentials .jwt file to remove the dependency with the jwt CLI
There was a problem hiding this comment.
Part of the reason for this is to also warm up the Auth endpoint. I found that individually calling the endpoints helps those endpoints perform faster.
There was a problem hiding this comment.
What I mean is that you could replace the jwt CLI command, for something like this: cat mock_credentials/trusted-intermediary-valid-token.jwt
There was a problem hiding this comment.
Ah I see, for some reason I thought the mock_credentials/trusted-intermediary-valid-token.jwt was the latter step in auth but that makes sense. I'll change this asap.
|
Run API in Docker During Load Test
This PR adds the logic to run the API in a docker container when performing the load test.
Issue
#1121