Support AWS provider v6

[lra]

#3384 blocked the use of aws v6.

This is understandable: this issue is to track the blocking issue that prevent the use of aws v6 when using this module.

[phfatemi]

it's not working

│ Error: Failed to query available provider packages │ │ Could not retrieve the list of available versions for provider hashicorp/aws: no available releases match the given constraints >= 4.33.0, >= 5.95.0, >= 6.0.0, < 6.0.0 │ │ To see which modules are currently depending on hashicorp/aws and what versions are specified, run the following command: │ terraform providers

[aschleifer]

it's not working

│ Error: Failed to query available provider packages │ │ Could not retrieve the list of available versions for provider hashicorp/aws: no available releases match the given constraints >= 4.33.0, >= 5.95.0, >= 6.0.0, < 6.0.0 │ │ To see which modules are currently depending on hashicorp/aws and what versions are specified, run the following command: │ terraform providers

This is only the limitation they put in place to avoid getting the new provider. There was an issue with self managed node groups ( #3383 ).

Not sure if there is already a PR open to fix the underlying issue.

I guess #3385 is the PR to fix that underlying issue.

[eugenia-ponomarenko]

I’m encountering the same issue. Many modules have recently been updated to depend on hashicorp/aws <= 6.0.0, which is now causing version conflicts. Here’s the error message I’m getting:

│ Error: Failed to query available provider packages
│
│ Could not retrieve the list of available versions for provider hashicorp/aws: no available releases match the given constraints >= 4.52.0, ~> 5.0, >= 6.0.0
│
│ To see which modules are currently depending on hashicorp/aws and what versions are specified, run the following command:
│     terraform providers

The constraints are overlapping in a way that makes it impossible to create a compatible version.

[bryantbiggs]

I’m encountering the same issue. Many modules have recently been updated to depend on hashicorp/aws <= 6.0.0, which is now causing version conflicts. Here’s the error message I’m getting:

│ Error: Failed to query available provider packages
│
│ Could not retrieve the list of available versions for provider hashicorp/aws: no available releases match the given constraints >= 4.52.0, ~> 5.0, >= 6.0.0
│
│ To see which modules are currently depending on hashicorp/aws and what versions are specified, run the following command:
│     terraform providers

The constraints are overlapping in a way that makes it impossible to create a compatible version.

this is only possible if you started updating to the bleeding edge without understanding the wider ramifications

[sanderjochems-capgemini]

Other Terraform AWS modules that are being used a lot like VPC, Lambda and S3 have set their minimal requirements to v6 of the AWS provider. When can we expect this module to support v6 too?

• https://github.com/terraform-aws-modules/terraform-aws-s3-bucket/releases/tag/v5.0.0
• https://github.com/terraform-aws-modules/terraform-aws-vpc/releases/tag/v6.0.0
• https://github.com/terraform-aws-modules/terraform-aws-lambda/releases/tag/v8.0.0
• https://github.com/terraform-aws-modules/terraform-aws-batch/releases/tag/v3.0.0
• https://github.com/terraform-aws-modules/terraform-aws-acm/releases/tag/v6.0.0

[bryantbiggs]

When can we expect this module to support v6 too?

You cannot expect anything from something that is provided for free

[sanderjochems-capgemini]

You cannot expect anything from something that is provided for free

I know, that's why I submitted the PR (#3385) to add support for v6 of the provider. I am just wondering what is still required before the major version can be released.

[bryantbiggs]

A breaking change is not trivial - there are a number of changes that have been pending and will be included along with support for v6.0 of the AWS provider

[sanderjochems-capgemini]

What are things we can do to help with the process of releasing the breaking changes?

[bryantbiggs]

Nothing but be patient and pin your provider to not use v6.0 until you have evaluated the ramifications

[bryantbiggs]

found my notes and copied them into an issue to share some of the changes that have been collected over the last 16 months #3394