InlineCommunicationEntry1

InlineCommunicationEntry1
InlineCommunicationEntry1
JSON Example
{
    "action": "string",
    "destination_groups": [
        "string"
    ],
    "direction": "string",
    "disabled": false,
    "logged": false,
    "notes": "string",
    "scope": [
        "string"
    ],
    "sequence_number": 0,
    "services": [
        "string"
    ],
    "source_groups": [
        "string"
    ],
    "tag": "string"
}
string
action
Optional

The action to be applied to all the services.

Possible values are : ALLOW, DROP, REJECT,
array of string
destination_groups
Optional

We need paths as duplicate names may exist for groups under different domains.In order to specify all groups, use the constant "ANY". This is case insensitive. If "ANY" is used, it should be the ONLY element in the group array. Error will be thrown if ANY is used in conjunction with other values.

string
direction
Optional

Define direction of traffic.

Possible values are : IN, OUT, IN_OUT,
boolean
disabled
Optional

Flag to disable the rule. Default is enabled.

boolean
logged
Optional

Flag to enable packet logging. Default is disabled.

string
notes
Optional

Text for additional notes on changes.

array of string
scope
Optional

The list of policy paths where the communication entry is applied Edge/LR/T0/T1/LRP/CGW/MGW/etc. Note that a given rule can be applied on multiple LRs/LRPs.

integer As int32 As int32
sequence_number
Optional

This field is used to resolve conflicts between multiple CommunicationEntries under CommunicationMap for a Domain If no sequence number is specified in the payload, a value of 0 is assigned by default. If there are multiple communication entries with the same sequence number then their order is not deterministic. If a specific order of communication entry is desired, then one has to specify unique sequence numbers or use the POST request on the communication entry entity with a query parameter action=revise to let the framework assign a sequence number

array of string
services
Optional

In order to specify all services, use the constant "ANY". This is case insensitive. If "ANY" is used, it should be the ONLY element in the services array. Error will be thrown if ANY is used in conjunction with other values.

array of string
source_groups
Optional

We need paths as duplicate names may exist for groups under different domains. In order to specify all groups, use the constant "ANY". This is case insensitive. If "ANY" is used, it should be the ONLY element in the group array. Error will be thrown if ANY is used in conjunction with other values.

string
tag
Optional

User level field which will be printed in CLI and packet logs.