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 transit gateway unbound gre tunnel connections #4213

Merged
merged 1 commit into from
Dec 13, 2022

Conversation

sarah-ulmer
Copy link
Contributor

Community Note

  • Please vote on this pull request by adding a 👍 reaction to the original pull request comment to help the community and maintainers prioritize this request
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for pull request followers and do not help prioritize the request

Output from acceptance testing:

export IBM_TG_CROSS_ACCOUNT_ID="<INSERT_ACCOUNT_ID>"
make testacc TESTARGS='-run=TestAccIBMTransitGatewayConnection_basic'
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test $(go list ./... |grep -v 'vendor') -v -run=TestAccIBMTransitGatewayConnection_basic -timeout 700m
=== RUN   TestAccIBMTransitGatewayConnection_basic
2022/12/01 14:33:04 Inside testAccCheckIBMTransitGatewayConnectionExists :  
--- PASS: TestAccIBMTransitGatewayConnection_basic (179.43s)
PASS
ok  	

@sarah-ulmer
Copy link
Contributor Author

@hkantare, @kavya498 Could you please review and merge this? Thank you

- `remote_bgp_asn` - (Optional, Forces new resource, Integer) - The remote network BGP ASN (will be generated for the connection if not specified). This field only applies to network type `gre_tunnel` and `unbound_gre_tunnel` connections.
- `remote_gateway_ip` - (Optional, Forces new resource, String) - The remote gateway IP address. This field only applies to network type `gre_tunnel` and `unbound_gre_tunnel` connections.
- `remote_tunnel_ip` - (Optional, Forces new resource, String) - The remote tunnel IP address. This field only applies to network type `gre_tunnel` and `unbound_gre_tunnel` connections.
- `zone` - (Optional, Forces new resource, String) - The location of the GRE tunnel. This field only applies to network type `gre_tunnel` and `unbound_gre_tunnel` connections.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We don't have attribute description for "base_network_type" which was recently added

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch, can't believe I missed that. It has been added.

@@ -45,20 +45,21 @@ In addition to the argument reference list, you can access the following attribu
Nested scheme for `connections`:
- `created_at` - (String) The date and time the connection is created.
- `id` - (String) The unique identifier for the transit gateway connection to network either `VPC`, `classic`.
- `base_connection_id` - The ID of a network_type `classic` connection a tunnel is configured over. This field only applies to network type `gre_tunnel` connections.
- `base_connection_id` - The ID of a network_type `classic` connection a tunnel is configured over. This field applies to network type `gre_tunnel` or `unbound_gre_tunnel` connections.
- `base_network_type` - The type of network the unbound gre tunnel is targeting. This field is required for network type `unbound_gre_tunnel`.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The indentation is missed out
Uploading Screenshot 2022-12-12 at 12.30.17 PM.png…

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The indentations have been fixed.

@sarah-ulmer
Copy link
Contributor Author

@hkantare thank you for your review. I fixed the doc errors you pointed out and caught a few more, which have been fixed.

Could you please review again?

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

Successfully merging this pull request may close these issues.

2 participants