fix!: CreateFleet API changes and robust cleanup #35
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.
What was the problem/requirement? (What/Why)
CreateFleet
API had a breaking change which moved the fleet's min/max capacity fields in the request.deadline_resources
fixture did not robustly clean up the farm/queue/fleet/queue-fleet-association resources if it encountered an error while part-way through creating themWhat was the solution? (How)
deadline_resources
fixture to have robust cleanup usingcontextlib.ExitStack
What is the impact of this change?
How was this change tested?
Ran the test in the worker agent codebase
and later:
Was this change documented?
No
Is this a breaking change?
Yes, the
resources.Fleet
API has changed and has a new requiredmax_worker_count
argument.