This resource manages clusters of import rules in a virtual router,
enforcing both the contents of individual rules as well as their
ordering. Rules are defined in a rule config block.

Although you cannot modify non-group import rules with this
resource, the position_keyword and position_reference parameters allow you
to reference some other import rule that already exists, using it as
a means to ensure some rough placement within the ruleset as a whole.

As is to be expected, if you are separating your deployment across
multiple plan files, make sure that at most only one plan specifies any given
absolute positioning keyword such as "top" or "directly below", otherwise
they'll keep shoving each other out of the way indefinitely.

Best practices are to specify one group as top (if you need it), one
group as bottom, then
all other groups should be above the first rule of the bottom group. You
do it this way because rules will natually be added at the tail end of the
ruleset, so they will always be after the first group, but what you want
is for them to be before the last group's rules.

position_keyword - (Optional) A positioning keyword for this group. This
can be before, directly before, after, directly after, top,
bottom, or left empty (the default) to have no particular placement. This
param works in combination with the position_reference param.

position_reference - (Optional) Required if position_keyword is one of the
"above" or "below" variants, this is the name of a non-group rule to use
as a reference to place this group.

rule - The import rule definition (see below). The import rule
ordering will match how they appear in the terraform plan file.

match_route_table - (Optional, PAN-OS 8.0+) Route table to match rule. Valid
values are unicast, multicast, or both. As of PAN-OS 8.1, there doesn't
seem to be a way to configure this in the GUI, it is always set to unicast.
Thus, if you're running this resource against PAN-OS 8.0+, the appropriate
thing to do is set this value to unicast as well to match the GUI functionality.

community_value - (Optional) If community_type is remove-regex,
append, or overwrite, the value associated with that setting. For the
append and overwrite types specifically, valid values for community_value
are no-export, no-advertise, local-as, or nopeer.