fix(aws_dynamodb_table): Specify "name" for GlobalSecondaryIndex in flattenTableGlobalSecondaryIndex
#41113
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.
Description
Resolves #41110. When applying an
aws_dynamodb_table
with a Global Secondary Index (GSI) against the DynamoDB local emulator, Terraform consistently shows diffs for the GSI, even though no actual changes are made.Investigation revealed that if
ProvisionedThroughput
is not configured, thename
property for the GSI remains empty. This PR ensures that thename
property is always set, preventing unnecessary diffs.Relations
Closes #41110 (
aws_dynamodb_table
GSI shows unexpected diffs when using DynamoDB local emulator)Output from Acceptance Testing
I was not able to setup environment for this test... 🙏