You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Run terraform -v to show the version. If you are not running the latest version of Terraform, please upgrade because your issue may have already been fixed.
The result (if the table is configured with a ttl) will import with ttl => false. Then subsequent plans will show a pending change. When you apply it returns a 400 on the API call but still writes the state file with the TTL change so that and subsequent apply's will be OK.
Important Factoids
Are there anything atypical about your accounts that we should know? For example: Running in EC2 Classic? Custom version of OpenStack? Tight ACLs?
References
Are there any other GitHub issues (open or closed) or Pull Requests that should be linked here? For example:
Terraform Version
Run
terraform -v
to show the version. If you are not running the latest version of Terraform, please upgrade because your issue may have already been fixed.terraform
v0.10.4
&&.terraform/plugins/darwin_amd64/terraform-provider-aws_v1.3.1_x4
Import for dynamodb_table does not import the TTL setting.
Affected Resource(s)
Please list the resources as a list, for example:
Terraform Configuration Files
n/a
Debug Output
Please provider a link to a GitHub Gist containing the complete debug output: https://www.terraform.io/docs/internals/debugging.html. Please do NOT paste the debug output in the issue; just paste a link to the Gist.
Panic Output
If Terraform produced a panic, please provide a link to a GitHub Gist containing the output of the
crash.log
.Expected Behavior
What should have happened?
Should Import the TTL from the dynamodb table.
Actual Behavior
What actually happened?
Doesn't import the TTL into the statefile.
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
terraform import aws_dynamodb_table.my_fancy_table TableName
The result (if the table is configured with a ttl) will import with ttl => false. Then subsequent plans will show a pending change. When you apply it returns a 400 on the API call but still writes the state file with the TTL change so that and subsequent apply's will be OK.
Important Factoids
Are there anything atypical about your accounts that we should know? For example: Running in EC2 Classic? Custom version of OpenStack? Tight ACLs?
References
Are there any other GitHub issues (open or closed) or Pull Requests that should be linked here? For example:
The text was updated successfully, but these errors were encountered: