Character limit of --dotenv in run-fargate

[hassy]

Discussed in #2518

^{Originally posted by jhengy February 27, 2024}
Hi all,

I was following the official CLI doc in using --dotenv to propagate environment variables from host to fargate containers. It was working fine at the beginning. However it seems like this approach does not scale with more variables. When I add a few more environment variables, I encounter the following error preventing artillery from starting the remote fargate containers:

invalidparameterexception: container overrides length must be at most 8192

Did a cursory search online and it seems that AWS imposes a limit of 8192 characters allowed for the override block in the ECS run task config. I suspect that artillery run-fargate uses it under the hood?

May I ask for advice on how to overcome this issue? Or is there any workaround for this? Thanks in advance

p.s. A bit more context, in our use case, we need to propagate environment variables such as access token with hundreds of characters in length.