Invalid AWS provider version 6.0.0 for ATF 1.20.0

[hanexl]

AFT Version:

1.20.0

Terraform Version & Provider Versions

terraform version

1.6.1

terraform providers

hashicorp/aws v6.0.0      <----------------- Note this one
hashicorp/archive v2.7.1
hashicorp/local v2.8.0
hashicorp/tls v4.2.1
hashicorp/random v3.8.1
hashicorp/time v0.13.1

Bug Description

The minimum AWS provider version is set to 6.0.0, but codestart is using AzureDevOps provider type.

AzureDevOps is only added to AWS provider version 6.8.0. I was on version 6.0.0 (as the minimum version set by AFT), but kept getting this error on terraform plan:

╷
│ Error: Invalid String Enum Value
│ 
│   with module.aft.module.aft_code_repositories.aws_codeconnections_connection.azuredevops,
│   on .terraform/modules/aft/modules/aft-code-repositories/codestar.tf line 71, in resource "aws_codeconnections_connection" "azuredevops":
│   71:   provider_type = "AzureDevOps"
│ 
│ The provided value does not match any valid values.
│ 
│ Path: provider_type
│ Given Value: AzureDevOps
│ Valid Values: [Bitbucket GitHub GitHubEnterpriseServer GitLab
│ GitLabSelfManaged ]
╵

To Reproduce

N/A

Expected behavior

The minimum required version here should change to 6.8.0

- version               = ">= 6.0.0, < 7.0.0"
+ version               = ">= 6.8.0, < 7.0.0"

Related Logs

Provided in "Bug Description" above.

Additional context

• AzureDevOps was added to supported enum types in aws-sdk-go-v2 (codeconnections 1.8.0) — CHANGELOG
• Terraform updated its codeconnections version to 1.8.0 in version 6.8.0

[wellsiau-aws]

@hossein-nexl - have you tried to re-run terraform init to bump your AWS provider?

[hanexl]

Yes @wellsiau-aws, we don't have a lock file, and therefore everytime we run the pipeline, it's a brand-new terraform init (not sure how everytime it downloads 6.0.0 even though there are newer versions 🤷)

However, I think that's besides the point. The point is that AFT 1.20.0 claims to work with 6.0.0 (i.e. >= 6.0.0) which is incorrect.

I do appreciate your help, but I have already worked my way around it by installing the exact 6.8.0 version; I was more reporting a bug than seeking a solution to my problem.