-
Notifications
You must be signed in to change notification settings - Fork 9.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
resource/aws_dynamodb_table: Allow disabling stream w/ empty view type #3197
Conversation
return fmt.Sprintf(` | ||
resource "aws_dynamodb_table" "basic-dynamodb-table" { | ||
name = "TerraformTestStreamTable-%d" | ||
read_capacity = 10 | ||
write_capacity = 20 | ||
hash_key = "TestTableHashKey" | ||
range_key = "TestTableRangeKey" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for making the configuration more relevant to what we're trying to test here 👍
I understand where this is change coming from and the Terraform schema helpers don't necessarily make this easy, but it now allows this incorrect configuration to passthrough to the apply stage and fail:
e.g.
|
d7cba3f
to
b52767a
Compare
b52767a
to
cd47170
Compare
cd47170
to
b77f4aa
Compare
b77f4aa
to
83dcb38
Compare
@bflad Added validation as discussed 😉 I also removed All DynamoDB acceptance tests are still passing. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
This has been released in terraform-provider-aws version 1.9.0. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
Fixes #1134
Despite
stream_view_type
being optional the validation is still being triggered which makes it impossible to parametrise the stream spec as described in #1134Test results