Closed YutongLi291 closed 1 day ago
Test for disallowing instance profile in worker was not creating the worker in the right fleet, causing unexpected behaviour.
Create the worker in the default fleet.
More robust tests
# Linux source .e2e_linux_infra.sh hatch run e2e-test # Windows source .e2e_windows_infra.sh hatch run e2e-test
No
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Issues 0 New issues 0 Accepted issues
Measures 0 Security Hotspots 0.0% Coverage on New Code 0.0% Duplication on New Code
See analysis details on SonarQube Cloud
What was the problem/requirement? (What/Why)
Test for disallowing instance profile in worker was not creating the worker in the right fleet, causing unexpected behaviour.
What was the solution? (How)
Create the worker in the default fleet.
What is the impact of this change?
More robust tests
How was this change tested?
Was this change documented?
No
Is this a breaking change?
No
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.