boto3 fails to submit Batch job with env var in eks pod properties override with a string value of ISO date

[igoichuk]

Describe the bug

I am submitting a job with an environment variable with the value 2024-08-01 that results in a type error. With any other value it works.

  File "/opt/homebrew/Caskroom/miniforge/base/envs/batch/lib/python3.9/site-packages/botocore/client.py", line 569, in _api_call
    return self._make_api_call(operation_name, kwargs)
  File "/opt/homebrew/Caskroom/miniforge/base/envs/batch/lib/python3.9/site-packages/botocore/client.py", line 980, in _make_api_call
    request_dict = self._convert_to_request_dict(
  File "/opt/homebrew/Caskroom/miniforge/base/envs/batch/lib/python3.9/site-packages/botocore/client.py", line 1047, in _convert_to_request_dict
    request_dict = self._serializer.serialize_to_request(
  File "/opt/homebrew/Caskroom/miniforge/base/envs/batch/lib/python3.9/site-packages/botocore/validate.py", line 381, in serialize_to_request
    raise ParamValidationError(report=report.generate_report())
botocore.exceptions.ParamValidationError: Parameter validation failed:
Invalid type for parameter eksPropertiesOverride.podProperties.containers[0].env[4].value, value: 2024-08-01, type: <class 'datetime.date'>, valid types: <class 'str'>

Expected Behavior

No reason to fail here

Current Behavior

The current behaviour is the error above.

Reproduction Steps

Submit EKS job with eksPropertiesOverride where you specify environment variables for the container. Make a value of any of the variables an ISO date string.

Possible Solution

code fix

Additional Information/Context

No response

SDK version used

boto3-1.35.7 botocore-1.35.7

Environment details (OS name and version, etc.)

Macos 14.6.1

[igoichuk]

I provided datatime.date not converted to a string in the parameters where it expected string, converting to a string resolved the issue

[github-actions]

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.