Closed tofupup closed 1 year ago
This issue has been automatically marked as stale because it has been open 30 days with no activity. Remove stale label or comment or this issue will be closed in 10 days
This issue was automatically closed because of stale in 10 days
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
Instance type t4g supports burstable CPU credits mode, but if
cpu_credits
is set when using theec2-instance
module it doesn't get set on the created resource. Any created t4g instance will use the "unlimited" setting.⚠️ Note
Before you submit an issue, please perform the following first:
.terraform
directory (! ONLY if state is stored remotely, which hopefully you are following that best practice!):rm -rf .terraform/
terraform init
Done
Versions
Module version [Required]: v4.1.4
Terraform version: Terraform v1.2.8 on linux_amd64
Provider version(s): provider registry.terraform.io/hashicorp/aws v4.29.0
Reproduction Code [Required]
Steps to reproduce the behavior:
standard
(instance defaults tounlimited
if not specified)terraform plan
output to see nocredit_specification
is being sentterraform apply
verify with AWS the instance is usingunlimited
credit specification usingaws ec2 describe-instance-credit-specifications --instance-ids
Expected behavior
credit_specification
to be set as specified, or be left unset if not specifiedActual behavior
credit_specification
is left unset inaws_instance
resource, causing it to default tounlimited
regardless of specified valueTerminal Output Screenshot(s)
Additional context
The
local.is_t_instance_type
function only includes the t2, t3, and t3a instance types, so won't automatically update with new instance types.