[BUG] `selector` and `selectorMatchOperator` properties shouldn't be defined required in `ApplicationGatewayFirewallExclusion`

[XiaofeiCao]

Hi team,

In portal, we can apply "Equals any" operator in exclusion rule for WAF_V2. In this case, both selector and selectorMatchOperator fields are null.

Request payload:

Response:

This contradicts the specs specification, where these properties are defined required.

SDK will validate the required restriction for fields during update, hence we can't add or update configuration rules with Equals any operator in them.

[ghost]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @appgwsuppgithub.

Issue Details

---

Hi team, In portal, we can apply "Equals any" operator in exclusion rule for WAF_V2. In this case, both `selector` and `selectorMatchOperator` fields are null.  Request payload:  Response:  This contradicts the [specs specification](https://github.com/Azure/azure-rest-api-specs/blob/main/specification/network/resource-manager/Microsoft.Network/stable/2022-01-01/applicationGateway.json#L3484-L3488), where these properties are defined required. SDK will validate the required restriction for fields during update, hence we can't add or update configuration rules with `Equals any` operator in them.

Author:	XiaofeiCao
Assignees:	-
Labels:	`Network - Application Gateway`, `Service Attention`
Milestone:	-

[XiaofeiCao]

WebApplicationFirewall is to be deprecated, so backend won't fix it. Closing this issue.

The issue here is in the webApplicationFirewallConfiguration. This is OLD way of doing WAF config and is on path to deprecation. New way is via WAF Policy. I don't think we need to fix this in swagger.