Patch for terraform AWS provider issue #6715

[userhas404d]

Workaround for AWS Provider version #6715

[userhas404d]

Note: pinning to provider version 1.43.0 and lower will prevent this error without requiring changes to the existing module.

Our org has given the aws provider maintainers a heads up regarding this issue in the current aws provider so hopefully we see a fix implemented soon.

[thrinadh238]

Hi

I need some information regarding this issue.

The above change is because of upgrading Terraform version or AWS made it mandatory???

[userhas404d]

@thrinadh238 a change was introduced in the terraform aws provider (v1.44.0 - see the 'heads up' link in my other comment for more details) that added the name and description options to the aws_ssm_maintenance_window_task resource. A welcome change, but one that does not allow them to be added conditionally (both are optional according to AWS). Pinning the terraform aws provider to versions less than 1.43 will avoid this issue unless they are explicitly defined in the resource definition as laid out in this PR.

TL;DR: This change is required because of a bug introduced in v1.44.0 of the terraform aws provider

[thrinadh238]

Hi,

Thanks for the quick reply.

Terraform documentation shows that it is optional. Please find the image below attached.

The version of AWS provider which you mentioned above is 1.43 but, we tried with below version
version = "~> 1.48.0".

It actually worked. It is not working with version 1.50