[bugfix] aws_rds_cluster: Fix inability to update serverlessv2_scaling_configuration.min_capacity
argument from 1
to 0
#44545
+14
−6
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.
Rollback Plan
If a change needs to be reverted, we will publish an updated version of the library.
Changes to Security Controls
Are there any changes to security controls (access controls, encryption, logging) in this pull request? If so, explain.
Description
min_capacity
could not be changed from1
to0
.verify.SuppressMissingOptionalConfigurationBlock
, configured as theDiffSuppressFunc
for theserverlessv2_scaling_configuration
block, is invoked not only for the block itself but also for its elements, includingmin_capacity
.0
and the old value is1
, which exactly matches the behavior observed formin_capacity
in this issue.serverlessv2_scaling_configuration.#
, which excludesmin_capacity
.min_capacity
is changed from1
to0
.Relations
Closes #44468
Output from Acceptance Testing