From de3735bd6f0b519139960097c1489aa5f8bc8499 Mon Sep 17 00:00:00 2001 From: Paul Hinze Date: Fri, 10 Apr 2015 14:29:31 -0500 Subject: [PATCH] docs: move aws SG tags from rules to resource fixes #1479 --- .../source/docs/providers/aws/r/security_group.html.markdown | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/website/source/docs/providers/aws/r/security_group.html.markdown b/website/source/docs/providers/aws/r/security_group.html.markdown index 314f64562..65c96e648 100644 --- a/website/source/docs/providers/aws/r/security_group.html.markdown +++ b/website/source/docs/providers/aws/r/security_group.html.markdown @@ -67,6 +67,7 @@ The following arguments are supported: egress rule. Each egress block supports fields documented below. VPC only. * `vpc_id` - (Optional) The VPC ID. +* `tags` - (Optional) A mapping of tags to assign to the resource. The `ingress` block supports: @@ -77,7 +78,6 @@ The `ingress` block supports: * `self` - (Optional) If true, the security group itself will be added as a source to this ingress rule. * `to_port` - (Required) The end range port. -* `tags` - (Optional) A mapping of tags to assign to the resource. The `egress` block supports: @@ -88,7 +88,6 @@ The `egress` block supports: * `self` - (Optional) If true, the security group itself will be added as a source to this egress rule. * `to_port` - (Required) The end range port. -* `tags` - (Optional) A mapping of tags to assign to the resource. ## Attributes Reference