aws_rds_cluster: Prevent error setting engine_mode and scaling_configuration in datasource #5660
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.
Fixes #5659
We have seen this type of regression before (#4922) due to sharing the same read functionality between the resource and data source, but not updating the data source schema. This completely separates the logic between two so they can be updated independently.
Also prevents other potential panics with:
DescribeDBClusters
response elementsnil
dereferences (uses SDK helper functions instead)Changes proposed in this pull request:
error setting scaling_configuration: Invalid address to set: []string{"scaling_configuration"}
inaws_rds_cluster
data sourceDescribeDBClusters
response elementsnil
dereference panicsOutput from acceptance testing: