non-autoscaling fleets workers are not deleted automatically from fleets. This causes errors when tests are run more than the amount of workers a fleet is allowed to launch.
What was the solution? (How)
Add autoscaling attribute to Fleet object.
When terminating an instances, if it is a non-autoscaling fleet, wait for the worker to be in a STOPPED state and then delete the worker from the fleet.
What is the impact of this change?
Allow the tests to run more than twice.
How was this change tested?
Tested using the Worker Agent tests.
Was this change documented?
No
Is this a breaking change?
Yes, changes the behaviour of how workers are stopped. We now pass a fleet object to the worker configuration instead of an id.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
What was the problem/requirement? (What/Why)
non-autoscaling fleets workers are not deleted automatically from fleets. This causes errors when tests are run more than the amount of workers a fleet is allowed to launch.
What was the solution? (How)
What is the impact of this change?
Allow the tests to run more than twice.
How was this change tested?
Tested using the Worker Agent tests.
Was this change documented?
No
Is this a breaking change?
Yes, changes the behaviour of how workers are stopped. We now pass a fleet object to the worker configuration instead of an id.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.