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
Throughput support is added to aws_launch_configuration resource in provider 3.44.0
⚠️ Note
Before you submit an issue, please perform the following first:
Remove the local .terraform directory (! ONLY if state is stored remotely, which hopefully you are following that best practice!): rm -rf .terraform/
Re-initialize the project root to pull down modules: terraform init
Re-attempt your terraform plan or apply and check if the issue still persists
When we provide gp3 as root_volume_type in workers_groups, and also update the throughput for the gp3 disk, the changes doesn't get reflected. A fix/improvement would be to add root_volume_throughput config here similar to the other configs
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.
Description
Throughput support is added to aws_launch_configuration resource in provider 3.44.0
When we provide
gp3
asroot_volume_type
inworkers_groups
, and also update the throughput for the gp3 disk, the changes doesn't get reflected. A fix/improvement would be to addroot_volume_throughput
config here similar to the other configsVersions
0.14.11
3.44.0
latest
Reproduction
Steps to reproduce the behavior:
Code Snippet to Reproduce
Expected behavior
Throughput configuration of
350 MiB/s
should have reflected in the provisioned volumeActual behavior
Throughput value is the default
125 MiB/s
Terminal Output Screenshot(s)
Additional context
The text was updated successfully, but these errors were encountered: