[Bug]: aws_codebuild_project compute_type doesn't support BUILD_GENERAL1_XLARGE

[lilanthadv]

Terraform Core Version

1.7.1

AWS Provider Version

5.2.0

Affected Resource(s)

aws_codebuild_project -> compute_type

Expected Behavior

Need to support BUILD_GENERAL1_LARGE type

AWS document

https://docs.aws.amazon.com/codebuild/latest/APIReference/API_ProjectEnvironment.html

AWS changed types BUILD_GENERAL1_LARGE -> BUILD_GENERAL1_XLARGE Use up to 72 GiB memory and 36 vCPUs for builds, depending on your environment type.

But that change is not reflected in the terraform. Terraform not support - BUILD_GENERAL1_XLARGE

Actual Behavior

Previously I used BUILD_GENERAL1_LARGE computer type for by code build and It's worked fine. But When I run "terraform plan" now. It's showing.

So I changed my terraform code to use "BUILD_GENERAL1_XLARGE". But it's throwing below error. I cannot use it anymore.

"Use up to 72 GiB memory and 36 vCPUs for builds, depending on your environment type"

Relevant Error/Panic Output Snippet

No response

Terraform Configuration Files

Steps to Reproduce

aws_codebuild_project - compute_type use BUILD_GENERAL1_XLARGE

Debug Output

No response

Panic Output

No response

Important Factoids

No response

References

No response

Would you like to implement a fix?

None

[github-actions[bot]]

Community Note

Voting for Prioritization

• Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
• Please see our prioritization guide for information on how we prioritize.
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

Volunteering to Work on This Issue

• If you are interested in working on this issue, please leave a comment.
• If this would be your first contribution, please review the contribution guide.

[jeremychauvet]

Hello @lilanthadv 👋🏼

I've read on the description you're using the version 5.2.0 of the provider, Am I right? This version has been released on Jun 9, 2023, and is currently outdated: latest version is v5.77.0.

Reviewing the AWS SDK Go v2 configuration, I've successfully found the configuration you're wanted to used, added 10 months ago.

➡️ In my opinion, the root cause of this issue is that the provider version you're using doesn't include the AWS SDK for Go version that introduced this feature.

Could you please update your configuration to use the latest provider version (5.77.0) and try again? If you need assistance with this step, feel free to let me know!