Skip to content
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

aws_dynamodb_table not updating when values changed #9671

Closed
ghost opened this issue Aug 7, 2019 · 3 comments · Fixed by #18215
Closed

aws_dynamodb_table not updating when values changed #9671

ghost opened this issue Aug 7, 2019 · 3 comments · Fixed by #18215
Assignees
Labels
service/dynamodb Issues and PRs that pertain to the dynamodb service.
Milestone

Comments

@ghost
Copy link

ghost commented Aug 7, 2019

This issue was originally opened by @dattim as hashicorp/terraform#22378. It was migrated here as a result of the provider split. The original body of the issue is below.


Terraform Version

Terraform v0.12.2

Your version of Terraform is out of date! The latest version
is 0.12.6. You can update by downloading from www.terraform.io/downloads.html
Wed Aug 07 10:30:28 

Expected Behavior

When I change global_secondary_index.read_capacity from 10 -> 60, terraform plan should show a change to the read_capacity for my global secondary index

Actual Behavior

When I change global_secondary_index.read_capacity from 10 -> 60, no changes are reported with terraform plan

Steps to Reproduce

Please list the full steps required to reproduce the issue, for example:

  1. Create a dynamo db table with terraform
    -- Set the read/write capacity for a global secondary index (not the table level read/write capacity) to 10 each
  2. terraform apply to create the table in AWS
  3. Change your terraform code to set the global secondary index read/write capacity to 60 each
  4. terraform plan to see no changes to the global secondary index capacities

Additional Context

I'm using a dynamic block for the global_secondary_index, and a variable block to populate it

Providers:

  • AWS 2.21.1 (tried with 2.22.0 too)
  • External 1.2.0
  • null 2.1.2
  • random 2.1.2
  • template 2.1.2

References

https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_UpdateGlobalSecondaryIndexAction.html
^ This should be possible, according to the API docs.

@github-actions github-actions bot added the needs-triage Waiting for first response or review from a maintainer. label Aug 7, 2019
@mlehner616
Copy link

This also affects changes to the primary sort keys. When changing from a string type to a Number for example. The change is ignored and results in "No Changes"

Expected behavior in this case would be a destroy/create operation on the entire table. I felt like this was related so I'm posting this here

@DrFaust92 DrFaust92 added the service/dynamodb Issues and PRs that pertain to the dynamodb service. label May 21, 2020
@YakDriver YakDriver removed the needs-triage Waiting for first response or review from a maintainer. label Apr 12, 2021
@YakDriver YakDriver self-assigned this Apr 12, 2021
@YakDriver YakDriver added this to the v3.37.0 milestone Apr 12, 2021
@ghost
Copy link
Author

ghost commented Apr 16, 2021

This has been released in version 3.37.0 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 for triage. Thanks!

@ghost
Copy link
Author

ghost commented May 13, 2021

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!

@ghost ghost locked as resolved and limited conversation to collaborators May 13, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
service/dynamodb Issues and PRs that pertain to the dynamodb service.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants