You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
and if port is not supplied it can use the current default of 80 for backwards compatibility. If this proposal is accepted I'm happy to attempt a PR for the change.
Many thanks
The text was updated successfully, but these errors were encountered:
The port used at target group creation is basically just a placeholder, it isn't actually used for routing traffic. When we register the targets, we specify the port that is actually used. This logic exists in model_build_targets.go.
Was there another reason behind needing to specify this port value?
Currently, all VPC Lattice target groups are created with the target group port as
80
which is not configurable.Reference:
Could we change this so that we can configure the target group port, possibly using the
TargetGroupPolicy
. It could look something like:and if
port
is not supplied it can use the current default of80
for backwards compatibility. If this proposal is accepted I'm happy to attempt a PR for the change.Many thanks
The text was updated successfully, but these errors were encountered: