ECS Fargate port mappings get overridden

[profsmallpine]

I am trying to attach two load balancer to an ecs fargate service. I am running faktory, which exposes ports 7419 + 7420. However, both will not get registered as targets. I can remove one, and the jobs target will work as expected, but I cannot get both working unless I manually register the target in the AWS console.

Steps to reproduce

const faktoryJobsListener = new awsx.lb.NetworkListener("faktory-jobs-traffic", { vpc, port: 7419 })
const faktoryWebListener = new awsx.lb.ApplicationListener("faktory-web-traffic", { vpc, port: 7420 });

const faktory = new awsx.ecs.FargateService("faktory", {
  taskDefinitionArgs: {
    containers: {
      faktory: {
        portMappings: [ faktoryJobsListener, faktoryWebListener ],
        ...
      },
    },
  }
})

I expected that I could direct traffic from two load balancers to a single fargate service, but only 1 listener registers a target.

[profsmallpine]

Looks like this has already been noticed and a fix was created: #698. Timeline to cut a release on this?