Rules with the same port_range but different protocols are treated as identical

searchspring / aws-security

Chef library cookbook for managing AWS Security Groups

Apache License 2.0

13 stars 13 forks source link

Rules with the same port_range but different protocols are treated as identical #21

Open jjhuff opened 9 years ago

jjhuff commented 9 years ago

I'm trying to open a range of ports on both udp and tcp. The second rule is never added since it's detected as already existing ("X already exists -- nothing to do").

My workaround is to specify slightly different port ranges so that they don't overlap...but that's awkward:)

bluecamel commented 9 years ago

Same issue here.