fix: fix failing dashboard lifecycle test for multi-account and region #9799
Conversation
This file contains 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
sannya-singal
added
the
semver: patch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Motivation
When using values other than
000000000000for account ID orus-east-1for region,cloudwatchtests should still create the consequent resources in corresponding accounts and region.Changes
This PR fixes all the failing tests
tests.aws.services.cloudwatch.test_cloudwatch.TestCloudwatch.test_dashboard_lifecycleby replacing the static value of regionus-east-1withTEST_AWS_REGION_NAME.Testing
The tests were failing previously when executed with a non-default account ID, set through environment variables (
TEST_AWS_ACCOUNT_ID=111111111111,TEST_AWS_ACCESS_KEY_ID=111111111111,TEST_AWS_REGION=us-west-1).