[BUG] AWS Batch Job’s cpu/mem not following Resources in the task decorator

[jw0515]

Describe the bug

After bumping flyte from v1.5.0 to v1.6.0 (also the same for v1.9.0, but 1.6.0 is the starting point that having this issue) I found that the task resource config doesn’t propagate to AWS Batch Job’s resource config, I define CPU and memory like this:

@task(requests=Resources(mem="16Gi", cpu="8"), task_config=AWSBatchConfig(platformCapabilities="EC2"))

But in AWS batch it’s always the default value that I defined in the helm chart:

  task_resource_defaults:
    task_resources:
      defaults:
        cpu: 1000m
        memory: 1000Mi
        storage: 1000Mi
      limits:
        cpu: 256
        memory: 512Gi
        storage: 512Gi

Expected behavior

AWS batch job using the resources I defined in the task decorator.

Additional context to reproduce

No response

Screenshots

No response

Are you sure this issue hasn't been raised already?

• Yes

Have you read the Code of Conduct?

• Yes

[wild-endeavor]

There's suspicion this was caused by flyteorg/flytepropeller#544 @hamersaw will be following up.

[github-actions]

Hello 👋, this issue has been inactive for over 9 months. To help maintain a clean and focused backlog, we'll be marking this issue as stale and will engage on it to decide if it is still applicable.
Thank you for your contribution and understanding! 🙏