[BUG] Microsoft.OperationalInsights @ 2022-10-01 - `clusters` PATCH operation missing response code

API Spec link

https://github.com/Azure/azure-rest-api-specs/blob/main/specification/operationalinsights/resource-manager/Microsoft.OperationalInsights/stable/2022-10-01/Clusters.json#L315-L321

API Spec version

2022-10-01

Describe the bug

The PATCH operation lists only 200 as a response, however the API responds with 202 when updating keyVaultProperties.

This is causing issues using an SDK generated from the REST API spec as it fails due to the unexpected status code.

Expected behavior

API spec lists all possible/expected response codes

Actual behavior

Missing 202 response code in API spec

Reproduction Steps

PATCH https://management.azure.com/subscriptions/<subscription_id>/resourceGroups/<resource_group_name>/providers/Microsoft.OperationalInsights/clusters/<cluster_name>?api-version=2022-10-01

{
	"properties": {
		"keyVaultProperties": {
			"keyName": "<key_name>",
			"keyVaultUri": "<key_vault_uri>",
			"keyVersion": "<key_version>"
		}
	}
}

Environment

No response

Open specification/operationalinsights/resource-manager/Microsoft.OperationalInsights/stable/2022-10-01/Clusters.json at lines 315-321 and inspect the clusters PATCH response definitions. Compare them with the reported keyVaultProperties update behavior and confirm that 202 should be documented alongside 200. Done when the API spec lists the expected response codes.