I have a workflow to deploy the Application hosted on the AWS ECS using Fargate.
The application is integrated with the AppMesh.
I have noticed that when the application is being deployed using the aws-ecs orb (aws-ecs/deploy-service-update) the task definition changes and the app mesh proxy settings are being removed.
The task definition is missing the following settings after the deployment:
“proxyConfiguration”: {
“type”: “APPMESH”,
“containerName”: “envoy”,
“properties”: [
{
“name”: “ProxyIngressPort”,
“value”: “15000”
},
{
“name”: “AppPorts”,
“value”: “5002”
},
{
“name”: “EgressIgnoredIPs”,
“value”: “169.254.170.2,169.254.169.254”
},
{
“name”: “IgnoredGID”,
“value”: “”
},
{
“name”: “EgressIgnoredPorts”,
“value”: “”
},
{
“name”: “IgnoredUID”,
“value”: “1337”
},
{
“name”: “ProxyEgressPort”,
“value”: “15001”
}
]
}
Did I miss something, or is there a an issue with the orb?