-
Notifications
You must be signed in to change notification settings - Fork 666
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
ibm_is_vpc_routing_table_route does not accept a VPN connection ID as next_hop #2270
Comments
The ibm_is_vpn_gateway_connection.VPNGatewayConnection1.id is combination of both VPN gateway/connection ..Can you please spilit the id using element to split the string
We will introduce an additional attribute |
Splitting the string does not help. It still throws the error: 'RouteTemplate.NextHop.RouteNextHopIP.Address' Error:Field validation for 'Address' failed on the 'validAddr' tag". |
@hbog We are working with respective service team ..We found the support is not enabled from SDK . |
Sorry for the ibm internal comment. See the SDK answer on this slack https://ibm-cloudplatform.slack.com/archives/CHY2EP4JJ/p1615338217001300?thread_ts=1614692283.003100&cid=CHY2EP4JJ https://github.ibm.com/cloud-api-docs/vpc/pull/107#pullrequestreview-7228195 includes this fix — will be included in today’s API refresh. |
@astha-jain is the SDK up to date? Can this be resolved, the work around is painful. |
I need a fix for this as well. |
This is supported in lates release |
It took me a couple of tries to get this to work. @hkantare is the value for next_hop what you expect?
Either way an example should provided. The docs https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/is_vpc_routing_table_route have a typo:
|
The value of next_hop should be the vpn connection id only (ibm_is_vpn_gateway_connection.route_transits.id is combination of both gateway/connectionid) |
https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/is_vpn_gateway_connection#attribute-reference |
Closing this issue |
Terraform Version
Terraform v0.14.6
Affected Resource(s)
Terraform Configuration Files
Debug Output
https://gist.github.com/hbog/6a54e8a3a8688c23f3f37d41c6a8e8d1
Expected Behavior
A route should be created with the vpn gateway connection as next-hop, as per the API documentation:
--next-hop value: If the action is 'deliver', the IP address or VPN connection ID of the next hop to which to route packets
Actual Behavior
The next-hop only accepts an IP address. A valid VPN connection ID is not accepted and throws an error: Error: Invalid json payload provided
Steps to Reproduce
apply
Important Factoids
N/A
References
N/A
The text was updated successfully, but these errors were encountered: