From 4c044f2b4e9b8b3f55b5928ee79d401813e95049 Mon Sep 17 00:00:00 2001 From: Joe Selman Date: Wed, 30 Aug 2017 12:19:50 -0700 Subject: [PATCH] Add ability to set priority on compute_firewall (#345) * Add ability to set priority on compute_firewall * Set the priority explicitly when upgrading v1->v0beta --- docs/r/compute_firewall.html.markdown | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/r/compute_firewall.html.markdown b/docs/r/compute_firewall.html.markdown index 67bcc378071..9f43b209c0b 100644 --- a/docs/r/compute_firewall.html.markdown +++ b/docs/r/compute_firewall.html.markdown @@ -52,6 +52,10 @@ The following arguments are supported: * `project` - (Optional) The project in which the resource belongs. If it is not provided, the provider project is used. +* `priority` - (Optional) The priority for this firewall. Ranges from 0-65535, inclusive. Defaults to 1000. Firewall + resources with lower priority values have higher precedence (e.g. a firewall resource with a priority value of 0 + takes effect over all other firewall rules with a non-zero priority). + * `source_ranges` - (Optional) A list of source CIDR ranges that this firewall applies to. Can't be used for `EGRESS`.