reset proxyConfiguration after deployment

[ghost]

heyja,

We are using this script and noticed, that the proxyConfiguration gets deleted once we deploy a new task revision.
Currently we are using envoy as a side-car container and need to have the proxyConfiguration in place in order to be able to integrate the service into the AWS-Mesh.

cheers,
Aven

[mauritz-lovgren]

Yes, and the "name": "ecs.capability.aws-appmesh" is removed from requiresAttributes section in the resulting task definition as well.

[forevermatt]

heyja,

We are using this script and noticed, that the proxyConfiguration gets deleted once we deploy a new task revision. Currently we are using envoy as a side-car container and need to have the proxyConfiguration in place in order to be able to integrate the service into the AWS-Mesh.

cheers, Aven

Hi @avendretter. It looks like proxyConfiguration may simply need to be added to this line in ecs-deploy (based on the AWS docs). Can you test that to confirm whether it fixes the issue for you?

---

Edit: Used more appropriate AWS docs URL for ECS task definition attributes.

[forevermatt]

Yes, and the "name": "ecs.capability.aws-appmesh" is removed from requiresAttributes section in the resulting task definition as well.

@mauritz-lovgren That sounds like it's probably a different issue. Would you mind submitting a new GitHub issue (and/or pull request) about that, to help us avoid losing track of your request when this issue is resolved?

[mauritz-lovgren]

@forevermatt :
I see now that the ecs.capability.aws-appmesh value is automatically set by AWS
when the proxyConfiguration section is added using the --proxy-configuration <json> option when registering the updated task def.