Remove requirement for unique gateway in route table

[zvymazal]

It's an incorrect assumption that there's only one network behind a gateway. It must for example be possible to route several networks through VPN gateway.

[hunner]

If you remove this validation and have a route table with multiple gateways, does puppet resource ec2_vpc_routetable report the correct gateways, or does it only report a single gateway? If puppet can't understand multiple gateways somewhere else in the module then this failure could be just to safeguard against other more obscure failures or non-idempotent puppet runs.

Thanks!

[prozach]

@zvymazal Would you mind coming back to address the question here please?

[zvymazal]

Hi @zleswomp, I believe it behaves correctly with multiple gateways because that's how we used it, but unfortunately I'm not working on that project anymore and cannot confirm on 100%.

[prozach]

This seems like a good change. I don't know how to validate it though.

[daveseff]

This may have been taken care of with my PR #505 I had to remove the explicit requirement for the gateway in order to accommodate the peering connections.