-
-
Notifications
You must be signed in to change notification settings - Fork 110
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
feat: adding the option to disable ttl once it was enable before #111
Conversation
Hi @joe-niland @Gowiem, this PR is open for some months ago, Do you have any comments? |
/terratest |
Hi @joe-niland @Gowiem, any additional requirements to merge this PR? |
@alfredo-gil can you update the readme (see the failing check) |
@alfredo-gil and also please update your branch from master |
Thanks @alfredo-gil for creating this pull request! A maintainer will review your changes shortly. Please don't be discouraged if it takes a while. While you wait, make sure to review our contributor guidelines. Tip Need help or want to ask for a PR review to be expedited?Join us on Slack in the |
what
The change aims to be able to disable the TTL once a dynamodb table was enabled before.
why
aws_dynamodb_table
resource if you change thevar.ttl_enabled = false
there are no changes on the infrastructure and the TTL is not disabled:No changes. Your infrastructure matches the configuration.
var.ttl_enabled = false
Do the plan and applyvar.ttl_attribute=""
or leave it empty to consolidate the state. If you don't do this second change your plan is going to say something like this and if you try to apply you will have an error...references