-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
Fix scenario tests failing with non-default region #9149
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
8840d6c
to
763508e
Compare
9363da1
to
4f09434
Compare
Other creds must be picked up from the execution role
S3 Image Test Results (AMD64 / ARM64) 2 files 2 suites 3m 16s ⏱️ Results for commit 1b03412. ♻️ This comment has been updated with latest results. |
LocalStack Community integration with Pro 2 files 2 suites 1h 22m 54s ⏱️ Results for commit e2c4a79. ♻️ This comment has been updated with latest results. |
680b153
to
1b03412
Compare
This reverts commit f83cf32.
721ac97
to
e2c4a79
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for jumping on this by improving and fixing the code 🚀 🙏
Summary
This PR fixes the following scenario tests that fail in non-default account/region:
tests.aws.scenario.bookstore.test_bookstore.TestBookstoreApplication.test_setup
tests.aws.scenario.bookstore.test_bookstore.TestBookstoreApplication.test_lambda_dynamodb
tests.aws.scenario.bookstore.test_bookstore.TestBookstoreApplication.test_search_books
Changes
Earlier, the credentials and region were hardcoded within the Lambda function code. Now, a proper IAM role is passed as a Lambda execution role. The function derives the proper credentials from this role and uses them for internal Boto instantiation.
Tests
See
ci/circleci: acceptance-tests
job for 1b03412 🟢 - this CI run used non-default test credentials, this demonstrates that the tests pass in such a situation.The affected tests have also been re-validated against AWS.