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

75 lines
2.4 KiB
Markdown
Raw Normal View History

Added LoadBalancer support for Cloudstack Provider PR is complete with docs and tests
2015-08-04 19:16:42 +02:00
---
layout: "cloudstack"
page_title: "CloudStack: cloudstack_loadbalancer_rule"
sidebar_current: "docs-cloudstack-resource-loadbalancer-rule"
description: |-
Creates a load balancer rule.
---
# cloudstack\_loadbalancer\_rule
Creates a loadbalancer rule.
## Example Usage
```
resource "cloudstack_loadbalancer_rule" "default" {
name = "loadbalancer-rule-1"
description = "Loadbalancer rule 1"
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
ip_address_id = "30b21801-d4b3-4174-852b-0c0f30bdbbfb"
Added LoadBalancer support for Cloudstack Provider PR is complete with docs and tests
2015-08-04 19:16:42 +02:00
algorithm = "roundrobin"
private_port = 80
public_port = 80
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
member_ids = ["f8141e2f-4e7e-4c63-9362-986c908b7ea7"]
Added LoadBalancer support for Cloudstack Provider PR is complete with docs and tests
2015-08-04 19:16:42 +02:00
}
```
## Argument Reference
The following arguments are supported:
* `name` - (Required) Name of the loadbalancer rule.
Changing this forces a new resource to be created.
* `description` - (Optional) The description of the load balancer rule.
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
* `ip_address_id` - (Required) Public IP address ID from where the network
traffic will be load balanced from. Changing this forces a new resource
to be created.
Added LoadBalancer support for Cloudstack Provider PR is complete with docs and tests
2015-08-04 19:16:42 +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
* `ipaddress` - (Required, Deprecated) Public IP address from where the
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
network traffic will be load balanced from. Changing this forces a new
resource to be created.
Added LoadBalancer support for Cloudstack Provider PR is complete with docs and tests
2015-08-04 19:16:42 +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
* `network_id` - (Optional) The network ID this rule will be created for.
Required when public IP address is not associated with any network yet
(VPC case).
* `network` - (Optional, Deprecated) The network this rule will be created
for. Required when public IP address is not associated with any network
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
yet (VPC case).
Added LoadBalancer support for Cloudstack Provider PR is complete with docs and tests
2015-08-04 19:16:42 +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
* `algorithm` - (Required) Load balancer rule algorithm (source, roundrobin,
leastconn). Changing this forces a new resource to be created.
Added LoadBalancer support for Cloudstack Provider PR is complete with docs and tests
2015-08-04 19:16:42 +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
* `private_port` - (Required) The private port of the private IP address
(virtual machine) where the network traffic will be load balanced to.
Added LoadBalancer support for Cloudstack Provider PR is complete with docs and tests
2015-08-04 19:16:42 +02:00
Changing this forces a new resource to be created.
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
* `public_port` - (Required) The public port from where the network traffic
will be load balanced from. 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
* `member_ids` - (Required) List of instance IDs to assign to the load balancer
rule. Changing this forces a new resource to be created.
* `members` - (Required, Deprecated) List of instances to assign to the load
balancer rule. Changing this forces a new resource to be created.
Added LoadBalancer support for Cloudstack Provider PR is complete with docs and tests
2015-08-04 19:16:42 +02:00
## Attributes Reference
The following attributes are exported:
* `id` - The load balancer rule ID.
* `description` - The description of the load balancer rule.