fix: Allow on_demand_throughput
optional values and disabling of table TTL
#93
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
Bumping provider version to include some provider bugfixes:
ttl[0].attribute_name
to be set whenttl[0].enabled
is falseon_demand_throughput
is excluded (this bug resulted in bothmax_read_request_units
andmax_write_request_units
being required to be set when both are optional)Motivation and Context
on_demand_throughput
hashicorp/terraform-provider-aws#39784Breaking Changes
No.
How Has This Been Tested?
examples/*
to demonstrate and validate my change(s)examples/*
projectspre-commit run -a
on my pull request