create listener rule instead of listener about terraform-aws-alb-ecs-task HOT 5 CLOSED

This module is designed to create a single task. Now that I think about it that way, your approach makes total sense.

from terraform-aws-alb-ecs-task.

hmm...Are we sure this is the approach we want to take?

I feel like logically it would make more sense to pass rules into the module than out of the module. If we really don't want to create the listener in the module, what advantage do we gain from creating rules in the module?

from terraform-aws-alb-ecs-task.

Yes. This approach has the advantage of being able to create a single listener that listens on 443 and routes requests to different ECS services depending on their host header like you'll see if you review my OF PR

from terraform-aws-alb-ecs-task.

Wouldn't you be able to do the same by passing a list of route objects into the module and using a for loop?

from terraform-aws-alb-ecs-task.

oh, my brain had the entirely wrong context in mind

from terraform-aws-alb-ecs-task.