module fails with aws provider v6.0

[oleg-opsfleet]

Description

Hello team and separate thanks to all contributors here.
After new aws provider v6.0 was released, the module now fails with

19:38:49.293 STDERR [ecs/services] terraform: │ Error: Unsupported block type
19:38:49.293 STDERR [ecs/services] terraform: │ 
19:38:49.293 STDERR [ecs/services] terraform: │   on ../../modules/service/main.tf line 635, in resource "aws_ecs_task_definition" "this":
19:38:49.293 STDERR [ecs/services] terraform: │  635:   dynamic "inference_accelerator" {
19:38:49.293 STDERR [ecs/services] terraform: │ 
19:38:49.293 STDERR [ecs/services] terraform: │ Blocks of type "inference_accelerator" are not expected here.
19:38:49.293 STDERR [ecs/services] terraform: ╵

This happens because this field was deleted from new version

resource/aws_ecs_task_definition: Remove inference_accelerator attribute. Amazon Elastic Inference reached end of life on April, 2024. (https://github.com/hashicorp/terraform-provider-aws/issues/42137)

When it will be possible, please update the module. 🙏

[bryantbiggs]

for now, just pin your required_providers to restrict the version to < 6.0

[mattWoolly]

I'm seeing this issue as well. Pinning an older version worked until today.

[bryantbiggs]

No, it's not module version - pin your required_providers for the AWS provider to < 6.0

[jpdoria]

I'm also getting this error. Unfortunately, pinning the AWS provider version to < 6.0.0. is not an option because it will break the VPC module in my project (for reference: terraform-aws-modules/terraform-aws-vpc#1207).

[albertocapella]

I fixed it in terragrunt adding the following block in a .hcl file

generate versions {
  path      = "versions.tf"
  if_exists = "overwrite"
  contents  = <<-EOF
  terraform {
    required_providers {
      aws = {
        source  = "hashicorp/aws"
        version = "< 6.0.0"
      }
    }
  }
  EOF
}

[rcpranavbansal]

when will this be updated ?

[bryantbiggs]

you can pin the version of the providers you use today, no module change required for that. upgrading to support v6 of the AWS provider will be handled here #217 (comment)

[rcpranavbansal]

Thanks!

[sadmdbrezack-metabolon]

Whats the ETA on 6.0 support. It's gonna take a very long time to fix this in my current terraform as some of my other modules are already running on 6.0.0.

[sfiguereo]

I am struggling with this as well and will have to fork the module as none of the alternatives given work for me. I wonder if the update will take days, weeks, months? It will be nice to have a ballpark idea so we dont have to reinvent the wheel.

[bryantbiggs]

It will be nice to have a ballpark idea so we dont have to reinvent the wheel.

I would not call forking and making small modification to suite your needs as "reinventing the wheel"

It would also be nice to be paid for what we provide for free, given how much users demand from us 🤷‍♂

[sfiguereo]

I was just respecfully asking for a ballpark so I can plan around, not demanding anything. I appreciate what you do to maintain this module and will definitively consider contributing to your efforts.