Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

provider/aws: fix panic when route has no cidr_block #2215

Merged
merged 1 commit into from
Jun 3, 2015
Merged

provider/aws: fix panic when route has no cidr_block #2215

merged 1 commit into from
Jun 3, 2015

Commits on Jun 3, 2015

  1. provider/aws: fix panic when route has no cidr_block 

    While cidr_block is required for static route creation, there are
apparently cases (involving some combination of VPNs, Customer Gateways,
and automatic route propogation) where the cidr_block can come back nil.
This means we cannot assume it's there in the set hash calculation.
    @phinze
    phinze committed Jun 3, 2015
    Configuration menu
    Copy the full SHA
    1caef30 View commit details
    Browse the repository at this point in the history