Priority value for lb.addListener should be validated by CDK

CDK should provide a synth time check to make sure that the priority value for a load balancer rule is not zero.

Use Case

When creating adding many targets to listeners I set priority to zero while looping through an array:

      listeners.forEach((listener, i) => {
        listener.addTargets(`Target${i}`, {
          pathPattern: `path-${i}`,
          priority: i,
          targets: [service],
          port: ports[i],
          protocol: elbv2.ApplicationProtocol.HTTP,
        });
      });

I was able to synth and diff without error. Then when I deployed I saw:

1 validation error detected: Value '0' at 'priority' failed to satisfy constraint: Member must have value greater than or equal to 1 (Service: AmazonElasticLoadBalancingV2; Status Code: 400; Error Code: ValidationError; Request ID: 79be03d3-3469-45c1-9dda-3e1e7049a6d6)

Proposed Solution

CDK should validate that priority !== 0 here.

• 👋 I may be able to implement this feature request
• ⚠️ This feature might incur a breaking change

---

This is a 🚀 Feature Request

[gary-cowell]

priority in ALB has long been an issue in various ways. Currently I’m using a lambda to return the next available priority, but ideally I’d like to just have to not specify it, and have CDK/CF choose a none conflicting priority for me. We may be unusual in that our patterns never overlap in any way so priority doesn’t actually matter much, but maybe we’re not that unusual in such a use case.

[hoegertn]

I am using a Lambda too for this purpose and I am thinking to implement this into CDK for a while now. Good to see, that I am not alone.