Files
opentf/website/source/docs/providers/cloudstack/r/network_acl.html.markdown
Sander van Harmelen 815c8840a7 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:28 +02:00

1.0 KiB

layout, page_title, sidebar_current, description
layout page_title sidebar_current description
cloudstack CloudStack: cloudstack_network_acl docs-cloudstack-resource-network-acl Creates a Network ACL for the given VPC.

cloudstack_network_acl

Creates a Network ACL for the given VPC.

Example Usage

resource "cloudstack_network_acl" "default" {
	name = "test-acl"
	vpc_id = "76f6e8dc-07e3-4971-b2a2-8831b0cc4cb4"
}

Argument Reference

The following arguments are supported:

  • name - (Required) The name of the ACL. Changing this forces a new resource to be created.

  • description - (Optional) The description of the ACL. Changing this forces a new resource to be created.

  • vpc_id - (Required) The ID of the VPC to create this ACL for. Changing this forces a new resource to be created.

  • vpc - (Required, Deprecated) The name or ID of the VPC to create this ACL for. Changing this forces a new resource to be created.

Attributes Reference

The following attributes are exported:

  • id - The ID of the Network ACL