Google Compute Engine Firewall Policy
This page shows how to write Terraform for Compute Engine Firewall Policy and write them securely.
The Firewall Policy in Compute Engine can be configured in Terraform with the resource name
google_compute_firewall_policy. The following sections describe how to use the resource and its parameters.
Example Usage from GitHub
An example could not be found in GitHub.
The following arguments are supported:
parent- (Required) The parent of the firewall policy.
short_name- (Required) User-provided name of the Organization firewall policy. The name should be unique in the organization in which the firewall policy is created. The name must be 1-63 characters long, and comply with RFC1035. Specifically, the name must be 1-63 characters long and match the regular expression a-z? which means the first character must be a lowercase letter, and all following characters must be a dash, lowercase letter, or digit, except the last character, which cannot be a dash.
description- (Optional) An optional description of this resource. Provide this property when you create the resource.
In addition to the arguments listed above, the following computed attributes are exported:
id- an identifier for the resource with format
creation_timestamp- Creation timestamp in RFC3339 text format.
fingerprint- Fingerprint of the resource. This field is used internally during updates of this resource.
id- The unique identifier for the resource. This identifier is defined by the server.
name- Name of the resource. It is a numeric ID allocated by GCP which uniquely identifies the Firewall Policy.
rule_tuple_count- Total count of all firewall policy rule tuples. A firewall policy can not exceed a set number of tuples.
self_link- Server-defined URL for the resource.
self_link_with_id- Server-defined URL for this resource with the resource id.
Explanation in Terraform Registry
Hierarchical firewall policy rules let you create and enforce a consistent firewall policy across your organization. Rules can explicitly allow or deny connections or delegate evaluation to lower level policies. Policies can be created within organizations or folders. This resource should be generally be used with
google_compute_firewall_policy_ruleFor more information see the official documentation