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.

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

Support for NAT GW as next hop in route entry #706

Closed
ghost opened this issue Jan 23, 2019 · 3 comments
Closed

Support for NAT GW as next hop in route entry #706

ghost opened this issue Jan 23, 2019 · 3 comments

Comments

@ghost
Copy link

ghost commented Jan 23, 2019

Hello,

According to the terraform documentation for alicloud_route_entry the following types of next hop are supported:

  • Instance (Default): Route the traffic destined for the destination CIDR block to an ECS instance in the VPC.
  • RouterInterface: Route the traffic destined for the destination CIDR block to a router interface.
  • VpnGateway: Route the traffic destined for the destination CIDR block to a VPN Gateway.
  • HaVip: Route the traffic destined for the destination CIDR block to an HAVIP.
  • NetworkInterface: Route the traffic destined for the destination CIDR block to an NetworkInterface.

The NAT gateway next hop type is missing here. The route can be created using portal UI, but such functionality is missing in terraform.

Thanks

@xiaozhu36
Copy link
Member

HI . @ninja-at-work Thanks for your feedback. It will be supported in the next version. Please be patient.

@xiaozhu36
Copy link
Member

HI @ninja-at-work This issue has been fixed by #713 . Please check.

@xiaozhu36
Copy link
Member

Fixed by 1.30.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant