r/aws_batch_compute_environment: Enforce no compute_resources block for UNMANAGED compute environments

[ewbankkit]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• 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
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

Relates: #16819.
Currently the aws_batch_compute_environment resource allows a compute_resources block to be specified when type = "UMANAGED" even though the AWS API does not allow this.
There is code in the resource implementation to ignore this attribute during Create and Read for UNMANAGED compute environments.

The correct validation should be done during terraform plan (via CustomizeDiff).
This is a breaking change as currently "valid" configurations will now become invalid.

New or Affected Resource(s)

• aws_batch_compute_environment

[github-actions]

This functionality has been released in v4.0.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

[github-actions]

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.