AWS Batch job definition always recreating if timeout is not provided.

[anishvm]

Once all the resources are created, on every subsequent run terraform always recreates aws batch job definition if value
for attempt_duration_seconds is null or not provided.

✋ I have searched the open/closed issues and my issue is not listed.

• Module version : v2.0.1

Terraform v1.5.3
on darwin_arm64

• provider registry.terraform.io/hashicorp/aws v5.9.0
• provider registry.terraform.io/hashicorp/external v2.3.1
• provider registry.terraform.io/hashicorp/local v2.4.0
• provider registry.terraform.io/hashicorp/null v3.2.1

Are you using workspaces? --> Yes
Have you cleared the local cache? --> Yes
List steps in order that led up to the issue you encountered -->

First terraform apply and once all the resources are created do apply or plan without changing any variables.

Expected behavior

A plan/apply should show no changes in output.

Actual behavior

Apply creates new job definition revision

Terminal Output Screenshot(s)

[github-actions]

This issue has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this issue will be closed in 10 days

[github-actions]

This issue was automatically closed because of stale in 10 days

[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.

[antonbabenko]

This issue has been resolved in version 3.0.0 🎉