Closed coderdude1 closed 4 months ago
Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.
If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!
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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Community Note
Terraform CLI and Terraform AWS Provider Version
Terraform CLI: 1.1.4 linux_amd64 AWS provider: 4.5.0 Atlantis and github enterprise
Affected Resource(s)
Terraform Configuration Files
I've included several steps of files that replicate the issue.
1. Starting Condition
Create table and GSI via terraform with
PAY_PER_REQUEST
, streams enabled, and PITR enabled.Results
2. Change table and GSI from on-demand to provisioned, with an autoscaler for the table AND the GSI
Results
3. Change the upper/lower limits via terraform (after manually fixing them)
Results
lifecycle ignore changes
(which I didn not try to replicate in the above terraform, but was added to prod code) is ignored for the GSIExpected Behavior
Actual Behavior
Steps to Reproduce
Apply the terraforms in steps as listed. Note the outputs.
Important Factoids
We can replicate this very easily simply by creating an on-demand table (the tags/stream/PITR won't be set on the replicas). When we terraform it to provisioned, the replicas always have issues with the autoscaler limits.
References
NA