fix: dynamically search for instance classes that have enough availability zones in the region #1412
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.
Summary
Dynamically search for an instance class that has enough availability zones for multi-az integration tests instead of using a hard coded option.
Description
The number of availability zone for each instance class and storage type combination changes due to availability on the service side.
We cannot use a hard coded storage type and instance class.
There isn't a way to determine whether the instance class supports mullti-az db clusters using the SDK, so we need to try the options one by one. For instance, querying the instance class
db.m6g.16xlarge
usingDescribeOrderableDbInstanceOptionsRequest
indicates the instance is multi-az capable (multiAZCapable == true
), but attempting to create a cluster with engine version 17.2 throws the following exception:Integration test runs:
Additional Reviewers
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.