elasticloadbalancingv2: fail to deploy integ test for NLB attributes

[badmintoncryer]

Describe the bug

Integ test for NLB attributes (integ.nlb-attributes.ts) fails to deploy due to an error.

new elbv2.NetworkLoadBalancer(stack, 'NLB', {
  vpc,
  crossZoneEnabled: true,
  deletionProtection: false,
  denyAllIgwTraffic: true, // This parameter is not configurable for IPV4 loadbalancer
  clientRoutingPolicy: elbv2.ClientRoutingPolicy.PARTIAL_AVAILABILITY_ZONE_AFFINITY,
});

The snapshot derived from this test is incorrect, and errors are occurring when making the related corrections.

Expected Behavior

Fix the integration test to ensure it deploys successfully.

• Remove the denyAllIgwTraffic setting from integ.nlb-attribute.ts
• Instead, set denyAllIgwTraffic in integ.nlb.dualstack.internal.ts.

Current Behavior

integ.nlb-attributes.ts integ test fails to deploy

Load balancer attribute key 'ipv6.deny_all_igw_traffic' is not supported on load balancers with IP address type 'ipv4'

Reproduction Steps

Specify denyAllIgwTraffic for IPV4 IP address type loadbalancer.

new elbv2.NetworkLoadBalancer(stack, 'NLB', {
  vpc,
  ipAddressType: elbv2.IpAddressType.IPV4,
  denyAllIgwTraffic: true, // This parameter is not configurable for IPV4 loadbalancer
});

Possible Solution

No response

Additional Information/Context

No response

CDK CLI Version

2.138.0

Framework Version

No response

Node.js Version

v20.10.0

OS

irreable

Language

TypeScript

Language Version

No response

Other information

No response

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.