ResiLien
/
terraform
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
terraform/website/source/docs/providers/cloudstack/r/secondary_ipaddress.html.ma...

54 lines
1.7 KiB
Markdown
Raw Normal View History

Updates and tweaks
2015-07-16 17:40:04 +02:00
---
layout: "cloudstack"
page_title: "CloudStack: cloudstack_secondary_ipaddress"
sidebar_current: "docs-cloudstack-resource-secondary-ipaddress"
description: |-
Assigns a secondary IP to a NIC.
---
# cloudstack\_secondary\_ipaddress
Assigns a secondary IP to a NIC.
## Example Usage
```
resource "cloudstack_secondary_ipaddress" "default" {
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:19 +02:00
virtual_machine_id = "server-1"
Updates and tweaks
2015-07-16 17:40:04 +02:00
}
```
## Argument Reference
The following arguments are supported:
Make the CloudStack provider more inline with the other provider It turns out all other providers use `ip_address` where the CloudStack provider uses `ipaddress`. To make this more consistent this PR deprecates `ipaddress` and adds `ip_address` where needed…
2016-04-04 22:13:27 +02:00
* `ip_address` - (Optional) The IP address to attach the to NIC. If not supplied
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:19 +02:00
an IP address will be selected randomly. Changing this forces a new resource
to be created.
Updates and tweaks
2015-07-16 17:40:04 +02:00
Make the CloudStack provider more inline with the other provider It turns out all other providers use `ip_address` where the CloudStack provider uses `ipaddress`. To make this more consistent this PR deprecates `ipaddress` and adds `ip_address` where needed…
2016-04-04 22:13:27 +02:00
* `ipaddress` - (Optional, Deprecated) The IP address to attach the to NIC. If
not supplied an IP address will be selected randomly. Changing this forces
a new resource to be created.
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:19 +02:00
* `nic_id` - (Optional) The NIC ID to which you want to attach the secondary IP
address. Changing this forces a new resource to be created (defaults to the
ID of the primary NIC)
Updates and tweaks
2015-07-16 17:40:04 +02:00
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:19 +02:00
* `nicid` - (Optional, Deprecated) The ID of the NIC to which you want to attach
the secondary IP address. Changing this forces a new resource to be created
(defaults to the ID of the primary NIC)
* `virtual_machine_id` - (Required) The ID of the virtual machine to which you
want to attach the secondary IP address. Changing this forces a new resource
to be created.
* `virtual_machine` - (Required, Deprecated) The name or ID of the virtual
machine to which you want to attach the secondary IP address. Changing this
forces a new resource to be created.
Updates and tweaks
2015-07-16 17:40:04 +02:00
## Attributes Reference
The following attributes are exported:
* `id` - The secondary IP address ID.