815c8840a7
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.
1.5 KiB
layout, page_title, sidebar_current, description
| layout | page_title | sidebar_current | description |
|---|---|---|---|
| cloudstack | CloudStack: cloudstack_ipaddress | docs-cloudstack-resource-ipaddress | Acquires and associates a public IP. |
cloudstack_ipaddress
Acquires and associates a public IP.
Example Usage
resource "cloudstack_ipaddress" "default" {
network_id = "6eb22f91-7454-4107-89f4-36afcdf33021"
}
Argument Reference
The following arguments are supported:
-
network_id- (Optional) The ID of the network for which an IP address should be acquired and associated. Changing this forces a new resource to be created. -
network- (Optional, Deprecated) The name or ID of the network for which an IP addess should be acquired and associated. Changing this forces a new resource to be created. -
vpc_id- (Optional) The ID of the VPC for which an IP address should be acquired and associated. Changing this forces a new resource to be created. -
vpc- (Optional, Deprecated) The name or ID of the VPC for which an IP address should be acquired and associated. Changing this forces a new resource to be created. -
project- (Optional) The name or ID of the project to deploy this instance to. Changing this forces a new resource to be created.
NOTE: Either network_id or vpc_id should have a value!
Attributes Reference
The following attributes are exported:
id- The ID of the acquired and associated IP address.ip_address- The IP address that was acquired and associated.