I think it might expect values as strings and it fails because at least of the values is boolean

I’d try to convert all values to strings first:

{"name": k, "value": str(v)} for k, v in self._config.env_vars.items()

(considering that all values

v

can be easily converted using

str(v)

)

Ok, you wrote that you have variable

debug: true

. I assume that

environment

in container definition stands for environment variables (then it makes sense that they are parsed later as strings). If so, you have to properly convert this boolean value to string -> that depends on how your application handles it. Just remember if you use

str(v)

, you’re gonna get upper-case versions:

>>> str(True)
'True'

>>> str(False)
'False'

If you want to fully control the conversion process, simply write a helper function that suits your needs:

def convert_to_env_string(v: Any) -> str:
  if isinstance(v, str):
    return v
  if isinstance(v, bool):
    return "true" if v else "false"
  ...
  raise ValueError("unsupported type")

and use it later when creating map for environment field:

{"name": k, "value": convert_to_env_string(v)} for k, v in self._config.env_vars.items()

and I wanted to avoid the conversion function. I'll keep it as is, knowing the limitation and have high hopes for aws native

I wouldn’t say so. In most cases, environment variables are treated as strings (same goes for k8s deployments or reading envs using

os.environ

in python) cause you cannot relay type information using them.