[EKS] Separating concurrency tag to be per region #37
+4
−4
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.
In the current state, if an EKS E2E test in a single region runs long then all regions will not be able to proceed until that one region is done running its test. This creates cross-region dependencies on our E2E test canary despite them being hosted on entirely separate infrastructure, and can cause false alarms to go off in all regions. As such, I've moved the concurrency tag accordingly and added the region to it so there is no interference
Description of changes:
group
attributeTesting:


I do not have the infrastructure set up in my personal fork/account to run this commit as a canary, but I ran the workflows in the following commits twice to show the logic is functional and when checking the workflow runs the one that started second did wait for the first to complete appropriately and only at a regional level. Commits:
Commit 1: link
Commit 2: link
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.