Hi, when running on ECSRun and setting env variables they are auto casting strings to ints which causes boto3 exception, is there a way to avoid auto casting?
k
Kevin Kho
08/03/2021, 9:26 PM
Hey @Nadav, is this when setting env vars on the agent? or through the RunConfig?
n
Nadav
08/03/2021, 9:41 PM
@Kevin Kho i set the variables on the cloud ui when creating a run
k
Kevin Kho
08/03/2021, 9:58 PM
Can you reproduce this with a minimal flow example? Does it also happen with Local Agent for you?
n
Nadav
08/03/2021, 10:11 PM
it won’t happen in local agent since this as far as i know an AWS exception when submit env variables to ECS, the type of of the variables values should be strings
k
Kevin Kho
08/03/2021, 10:13 PM
Ohh gotcha! I’ll try to replicate this tonight.
n
Nadav
08/03/2021, 10:27 PM
thanks
k
Kevin Kho
08/04/2021, 2:57 AM
I replicated this. So when I go to the UI and do key=test, value=1, this becomes an integer but if I do key=test and value=“1” and this worked.
When I used JSON to input though, automatic conversation was applied. Will talk to the team about this.