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

Unable to Successfully Import Existing DynamoDB Table with Different Target Read/Write Scaling Values #91

Open
1 task done
deer-prudence opened this issue Oct 29, 2024 · 0 comments

Comments

@deer-prudence
Copy link

deer-prudence commented Oct 29, 2024

Description

  • ✋ I have searched the open/closed issues and my issue is not listed.

Versions

  • Module version [Required]: v4.2.0

  • Terraform version:

OpenTofu v1.7.3
on darwin_arm64
+ provider registry.opentofu.org/hashicorp/aws v5.73.0

Reproduction Code [Required]

Steps to reproduce the behavior:

  1. Import an existing DynamoDB table that already has target tracking scaling enabled.
  2. The DynamoDB table should have a different target_value for the read and write autoscaling policies for autoscaling indices.
  3. In order to populate these values, the module only provides one argument. However, these values can differ between read and write policies.

Expected behavior

autoscaling_indexes = {
    "org_id_index" = {
      ...
     target_read_value = x
     target_write_value = y
    }
  }

Actual behavior

autoscaling_indexes = {
    "org_id_index" = {
      ...
     target_value = x
    }
  }

Output:
Either the read or write aws_appautoscaling_policy.index_(read|write)_policy policy being modified.

Additional context

The values are populated here for read and here for write.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant