From eb977aa5fd76356937e85d4f69718f91a293c033 Mon Sep 17 00:00:00 2001 From: Travis Truman Date: Mon, 27 Apr 2015 10:05:54 -0400 Subject: [PATCH] Clarify that the security group resource can have many rules --- .../openstack/r/compute_secgroup_v2.html.markdown | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/website/source/docs/providers/openstack/r/compute_secgroup_v2.html.markdown b/website/source/docs/providers/openstack/r/compute_secgroup_v2.html.markdown index 5b9538793d..1c7afd5b3e 100644 --- a/website/source/docs/providers/openstack/r/compute_secgroup_v2.html.markdown +++ b/website/source/docs/providers/openstack/r/compute_secgroup_v2.html.markdown @@ -22,6 +22,12 @@ resource "openstack_compute_secgroup_v2" "secgroup_1" { ip_protocol = "tcp" cidr = "0.0.0.0/0" } + rule { + from_port = 80 + to_port = 80 + ip_protocol = "tcp" + cidr = "0.0.0.0/0" + } } ``` @@ -42,7 +48,8 @@ The following arguments are supported: * `rule` - (Optional) A rule describing how the security group operates. The rule object structure is documented below. Changing this updates the - security group rules. + security group rules. As shown in the example above, multiple rule blocks + may be used. The `rule` block supports: