-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow dynamic port mapping #1
Comments
Good idea. Will investigate. |
Actually, it might not make sense since you seem to target elb rather than alb. In my scenario, I would also want to use target_group_arn rather than elb_arn so there seems to be a gap between the logic of the two. |
@agalazis I think it still makes sense as you may want to map to a different port on the host regardless. We plan to support ALBs in future as well so I'll try and get this added in. |
Any updates on this? |
@ShahNewazKhan sorry, haven't had a chance to get to this. I'll happily accept a pull request though. |
Support for target_group_arn has been added as of 0.6.0 for terraform 0.11 and 1.1.0 for terraform 0.12. |
Allow passing in container and service port separately. This way when service port is zero we can achieve dynamic port mapping without passing custom task definition
The text was updated successfully, but these errors were encountered: