At the moment when specifying env vars, it merges existing env vars from the last revision of the task definition family, which is not what I would expect.
The current behaviour requires manual creation of task definition revision if you want to remove previously existing env vars.
At the moment when specifying env vars, it merges existing env vars from the last revision of the task definition family, which is not what I would expect.
The current behaviour requires manual creation of task definition revision if you want to remove previously existing env vars.