-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
dynamodb/table: Fix ability to disable dynamodb table ttl #40046
Conversation
Community NoteVoting for Prioritization
For Submitters
|
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 🚀
Looks good! Just one suggestion on gating the new test.
PreConfig: func() { | ||
// AWS does not allow disabling TTL for an hour after it was enabled. Otherwise, it | ||
// will return the following error: ValidationException: Time to live has been | ||
// modified multiple times within a fixed interval | ||
time.Sleep(60 * time.Minute) | ||
}, |
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.
Should we consider gating this behind an environment variable (ENABLE_DYNAMODB_TTL_DISABLE
or similar) in addition to the standard -short
directive?
The other table tests aren't quite on the order of hours, so I could see this causing friction when running acceptance tests to validate changes to other arguments.
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.
My concern there is that the test wouldn't be run ever then.... I definitely see your point and maybe we circle back and add it but would like to see it run sometimes to make sure we don't break it again for a little bit.
This functionality has been released in v5.75.1 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
Description
Brief history:
ttl.0.attribute_name
going out to AWS but not coming backttl.attribute_name
is set when not enabled #37991 attempted to fix the diff by applying validation preventingttl.0.attribute_name
from being set ifttl.0.enabled
isfalse
. That fixed the diff but caused another problem.ttl.0.attribute_name
, even though AWS will not return it. resource/aws_dynamodb_table: Fixes perpetual diff whenttl.attribute_name
is set when not enabled #37991 made it impossible to disable TTL.ttl.0.attribute_name
from being set ifttl.0.enabled
isfalse
and addresses the diff issue with aDiffSuppressFunc
.Relations
Closes #39195
Relates #37991
References
ttl.attribute_name
is set when not enabled #37991Output from Acceptance Testing