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

65 lines
1.9 KiB
Markdown
Raw Normal View History

First release of a provider for CloudStack Of course not all resources are covered by this first release, but there should be enough resources available to handle most common operations. Tests and docs are included.
2014-12-10 22:20:52 +01:00
---
layout: "cloudstack"
page_title: "CloudStack: cloudstack_firewall"
sidebar_current: "docs-cloudstack-resource-firewall"
description: |-
website: address spelling mistakes, casing and links
2015-01-03 19:31:53 +01:00
Creates firewall rules for a given IP address.
First release of a provider for CloudStack Of course not all resources are covered by this first release, but there should be enough resources available to handle most common operations. Tests and docs are included.
2014-12-10 22:20:52 +01:00
---
# cloudstack\_firewall
website: address spelling mistakes, casing and links
2015-01-03 19:31:53 +01:00
Creates firewall rules for a given IP address.
First release of a provider for CloudStack Of course not all resources are covered by this first release, but there should be enough resources available to handle most common operations. Tests and docs are included.
2014-12-10 22:20:52 +01:00
## Example Usage
```
resource "cloudstack_firewall" "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
ip_address_id = "30b21801-d4b3-4174-852b-0c0f30bdbbfb"
First release of a provider for CloudStack Of course not all resources are covered by this first release, but there should be enough resources available to handle most common operations. Tests and docs are included.
2014-12-10 22:20:52 +01:00
rule {
Change all firewall related resources to take a cidr_list Also some additional tweaks to improve performance and add in a little concurrency to speed things up a little.
2015-12-03 11:10:42 +01:00
cidr_list = ["10.0.0.0/8"]
First release of a provider for CloudStack Of course not all resources are covered by this first release, but there should be enough resources available to handle most common operations. Tests and docs are included.
2014-12-10 22:20:52 +01:00
protocol = "tcp"
ports = ["80", "1000-2000"]
}
}
```
## Argument Reference
The following arguments are supported:
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) The IP address ID for which to create the
firewall rules. Changing this forces a new resource to be created.
First release of a provider for CloudStack Of course not all resources are covered by this first release, but there should be enough resources available to handle most common operations. Tests and docs are included.
2014-12-10 22:20:52 +01:00
Adding/updating the docs to reflect the changes in the provider
2015-01-16 17:23:27 +01:00
* `managed` - (Optional) USE WITH CAUTION! If enabled all the firewall rules for
this IP address will be managed by this resource. This means it will delete
all firewall rules that are not in your config! (defaults false)
* `rule` - (Optional) Can be specified multiple times. Each rule block supports
fields documented below. If `managed = false` at least one rule is required!
First release of a provider for CloudStack Of course not all resources are covered by this first release, but there should be enough resources available to handle most common operations. Tests and docs are included.
2014-12-10 22:20:52 +01:00
Make the concurrence for applying rules configurable
2016-01-21 21:30:54 +01:00
* `parallelism` (Optional) Specifies how much rules will be created or deleted
concurrently. (defaults 2)
First release of a provider for CloudStack Of course not all resources are covered by this first release, but there should be enough resources available to handle most common operations. Tests and docs are included.
2014-12-10 22:20:52 +01:00
The `rule` block supports:
Change all firewall related resources to take a cidr_list Also some additional tweaks to improve performance and add in a little concurrency to speed things up a little.
2015-12-03 11:10:42 +01:00
* `cidr_list` - (Required) A CIDR list to allow access to the given ports.
First release of a provider for CloudStack Of course not all resources are covered by this first release, but there should be enough resources available to handle most common operations. Tests and docs are included.
2014-12-10 22:20:52 +01:00
* `protocol` - (Required) The name of the protocol to allow. Valid options are:
`tcp`, `udp` and `icmp`.
* `icmp_type` - (Optional) The ICMP type to allow. This can only be specified if
the protocol is ICMP.
* `icmp_code` - (Optional) The ICMP code to allow. This can only be specified if
the protocol is ICMP.
Revert "docs: consistent use of array configuration syntax" This reverts commit 4893eb8b559c3664377c5c5aab4b30f82caa922b.
2015-01-14 18:28:25 +01:00
* `ports` - (Optional) List of ports and/or port ranges to allow. This can only
First release of a provider for CloudStack Of course not all resources are covered by this first release, but there should be enough resources available to handle most common operations. Tests and docs are included.
2014-12-10 22:20:52 +01:00
be specified if the protocol is TCP or UDP.
## Attributes Reference
The following attributes are exported:
Adding tests and docs for the new VPN resources And did some (very) minor refactoring in the existing docs
2015-03-09 14:00:29 +01:00
* `id` - The IP address ID for which the firewall rules are created.