The acceptance tests are pulling a keystore.json file form s3 in order to run, but this should be properly stubbed out so that we aren't reaching out to s3 in our test environment.
The S3 bucket that did contain the keystore.json file has been destroyed and it is expected that the automated tests are now not working
From slack:
[tests] do exist, but i don’t want them to be reaching into s3 anyway so next time we have to update oidc we’ll just need to properly stub that out
Slack Message
The acceptance tests are pulling a keystore.json file form s3 in order to run, but this should be properly stubbed out so that we aren't reaching out to s3 in our test environment.
The S3 bucket that did contain the keystore.json file has been destroyed and it is expected that the automated tests are now not working
From slack:
[tests] do exist, but i don’t want them to be reaching into s3 anyway so next time we have to update oidc we’ll just need to properly stub that out
Slack Message