89bacc0b15
Ingress and egress rules given a "-1" protocol don't have ports when Read out of AWS. This results in hashing problems, as a local config file might contain port declarations AWS can't ever return. Rather than making ports optional fields, which carries with it a huge headache trying to distinguish between zero-value attributes (e.g. 'to_port = 0') and attributes that are simply omitted, simply force the user to opt-in when using the "-1" protocol. If they choose to use it, they must now specify "0" for both to_port and from_port. Any other configuration will error. |
||
|---|---|---|
| .. | ||
| atlas | ||
| aws | ||
| cloudflare | ||
| cloudstack | ||
| consul | ||
| digitalocean | ||
| dme | ||
| dnsimple | ||
| docker | ||
| heroku | ||
| mailgun | ||
| null | ||
| openstack | ||
| terraform | ||