Example data:
Nested Schema for rules.match_entries
Required:
• type (String) Type of match entry
o Choices: sourceFqdnList, sourceDataPrefixList, sourceGeoLocationList, sourcePortList, destinationFqdnList, destinationDataPrefixList, destinationGeoLocationList, destinationPortList, appList, protocolNameList, sourceIp, sourcePort, sourceFqdn, destinationIp, destinationPort, sourceGeoLocation, destinationGeoLocation, protocolName, protocol, app, ruleSetList
Note: We need to add destination_fqdn in Nested Schema for rules.match_entries
danischm
commented
3 months ago
We are unable to create destination_fqdn module. In Nested Schema for rules.match_entries There is no destination_fqdn.
Example data: Nested Schema for rules.match_entries Required: • type (String) Type of match entry o Choices: sourceFqdnList, sourceDataPrefixList, sourceGeoLocationList, sourcePortList, destinationFqdnList, destinationDataPrefixList, destinationGeoLocationList, destinationPortList, appList, protocolNameList, sourceIp, sourcePort, sourceFqdn, destinationIp, destinationPort, sourceGeoLocation, destinationGeoLocation, protocolName, protocol, app, ruleSetList Note: We need to add destination_fqdn in Nested Schema for rules.match_entries
While creating the sdwan_zone_based_fw_policy_definition module we are getting error.
Error:
│ Attribute rules[1].match_entries[2].type value must be one of: ["sourceFqdnList" "sourceDataPrefixList" "sourceGeoLocationList" "sourcePortList"
│ "destinationFqdnList" "destinationDataPrefixList" "destinationGeoLocationList" "destinationPortList" "appList" "protocolNameList" "sourceIp"
│ "sourcePort" "sourceFqdn" "destinationIp" "destinationPort" "sourceGeoLocation" "destinationGeoLocation" "protocolName" "protocol" "app" │ "ruleSetList"], got: "destinationFqdn"
Refer: We are unable to create destination fqdn.docx