Files
opentf/website/source/docs/providers/cloudstack/r/vpn_gateway.html.markdown
Sander van Harmelen 815c8840a7 Refactor the use of names vs IDs for parameters referencing other TF resources
We have a curtesy function in place allowing you to specify both a
`name` of `ID`. But in order for the graph to be build correctly when
you recreate or taint stuff that other resources depend on, we need to
reference the `ID` and *not* the `name`.

So in order to enforce this and by that help people to not make this
mistake unknowingly, I deprecated all the parameters this allies to and
changed the logic, docs and tests accordingly.
2016-04-11 17:14:28 +02:00

929 B

layout, page_title, sidebar_current, description
layout page_title sidebar_current description
cloudstack CloudStack: cloudstack_vpn_gateway docs-cloudstack-resource-vpn-gateway Creates a site to site VPN local gateway.

cloudstack_vpn_gateway

Creates a site to site VPN local gateway.

Example Usage

Basic usage:

resource "cloudstack_vpn_gateway" "default" {
    vpc_id = "f8141e2f-4e7e-4c63-9362-986c908b7ea7"
}

Argument Reference

The following arguments are supported:

  • vpc_id - (Required) The ID of the VPC for which to create the VPN Gateway. Changing this forces a new resource to be created.

  • vpc - (Required, Deprecated) The name or ID of the VPC for which to create the VPN Gateway. Changing this forces a new resource to be created.

Attributes Reference

The following attributes are exported:

  • id - The ID of the VPN Gateway.
  • public_ip - The public IP address associated with the VPN Gateway.