resource/aws_dynamodb_table: Don't fall back to primary hash key in LSI #3176
Labels
breaking-change
Introduces a breaking change in current functionality; usually deferred to the next major release.
bug
Addresses a defect in current functionality.
service/dynamodb
Issues and PRs that pertain to the dynamodb service.
stale
Old or inactive issues managed by automation, if no further action taken these will get closed.
Terraform Version
1.8.0
Terraform Configuration Files
The DynamoDB table resource is a bit (confusingly) magical in the sense that it automatically falls back to
hash_key
if there was nohash_key
set inlocal_secondary_index.*.hash_key
.This is a reminder to revisit the decision and align the implementation more with the API - i.e. just let users be explicit and let API error out if they don't provide
local_secondary_index.*.hash_key
.References
The text was updated successfully, but these errors were encountered: