Exclude GET verb from LroExtension rule validation

[AkhilaIlla]

#549

This PR contains updates to
RPC-GET-V1-01(GetOperation200): to allow GET with 202 response code and
RPC-Post-V1-09(LroExtension): to exclude GET from x-ms-long-running-operation presence validation
in order to support pooling kinda API's

"/providers/Microsoft.Subscription/subscriptionOperations/{operationId}": {
      "get": {
        "description": "Get the status of the pending Microsoft.Subscription API operations.",
        "operationId": "SubscriptionOperation_Get",
        "x-ms-examples": {
          "getPendingSubscriptionOperations": {
            "$ref": "./examples/getSubscriptionOperation.json"
          }
        },
        "responses": {
          "200": {
            "description": "Successful completion of the asynchronous operation",
            "schema": {
              "$ref": "#/definitions/SubscriptionCreationResult"
            }
          },
          "202": {
            "description": "Accepted. Subscription update is in progress.",
            "headers": {
              "Location": {
                "description": "The URL where the status of the asynchronous operation can be checked.",
                "type": "string"
              },
              "Retry-After": {
                "description": "The amount of delay to use while the status of the operation is checked. The value is expressed in seconds.",
                "type": "integer",
                "format": "int64"
              }
            }
          },
          "default": {
            "description": "Error response describing why the operation failed.",
            "schema": {
              "$ref": "../../../../../common-types/resource-management/v5/types.json#/definitions/ErrorResponse"
            }
          }
        },
        "parameters": [
          {
            "name": "operationId",
            "in": "path",
            "description": "The operation ID, which can be found from the Location field in the generate recommendation response header.",
            "required": true,
            "type": "string"
          },
          {
            "$ref": "#/parameters/apiVersionParameter"
          }
        ]
      }
    },

[rkmanda]

Lets use the new template that was decided for the help files. #Closed

[rkmanda]

cant find the link where this was documented. Please check with Tejaswi

[AkhilaIlla]

https://github.com/Azure/azure-openapi-validator/blob/main/CONTRIBUTING.md#how-to-write-a-new-validation-rule-using-typescript

[rkmanda]

include good and bad examples #Closed

[rkmanda]

  "comment": "Update RPC-GET-V1-01(GetOperation200) to allow GET with 202 response code if the GET represents the location header polling url. Update RPC-Post-V1-09(LroExtension) to exclude GET from x-ms-long-running-operation presence validation",

#Closed

[AkhilaIlla]

I didnt add
"if the GET represents the location header polling url" cause that isnt being checked in this rule

[rkmanda]

        description: "Operations with a 202 response must specify `x-ms-long-running-operation: true`.",

Make it explicit everywhere that this does not apply to Get including the help file #Closed

---

Refers to: packages/rulesets/generated/spectral/az-arm.js:891 in 290a9a6. [](commit_id = 290a9a6, deletion_comment = False)

[rkmanda]

why not make it an inclusion list for 200, 202 instead of an exclusion list for 201, 203, 204? #Closed

[rkmanda]

That way we get broader coverage

[AkhilaIlla]

thats a good point!
But we'd not be able to use the core function

[rkmanda]

🕐

[rkmanda]