[BUG] PUT operation for privateendpoint connection approval is not idempotent

[krupakar1329]

API Spec link

https://learn.microsoft.com/en-us/rest/api/storagerp/private-endpoint-connections/put?view=rest-storagerp-2023-05-01&tabs=HTTP

API Spec version

2023-05-01

Describe the bug

Trying to approve the private endpoint connection , which is in Approved state shouldnt throw error for idempotent operations.
But getting

│ {
│   "error": {
│     "code": "InvalidValuesForRequestParameters",
│     "message": "Values for request parameters are invalid: privateLinkServiceConnectionState.status."
│   }

Expected behavior

Api can be hit any number of times for PUT operation

Actual behavior

│ {
│   "error": {
│     "code": "InvalidValuesForRequestParameters",
│     "message": "Values for request parameters are invalid: privateLinkServiceConnectionState.status."
│   }

Reproduction Steps

1. Create a manual approval private endpoint
2. Use https://learn.microsoft.com/en-us/rest/api/storagerp/private-endpoint-connections/put?view=rest-storagerp-2023-05-01&tabs=HTTP to approve private endpoint
3. Run step2 again , it shouldn't throw error. but it giving error

Environment

No response

[v-jiaodi]

@golddove Please help take a look, thanks.

[v-jiaodi]

@triciarosario Please help take a look, thanks.

[kamilzzz]

+1, this is not idempotent and should be fixed on the service side.

We cannot redeploy ARM/Bicep because subsequent deployments fail with Values for request parameters are invalid: privateLinkServiceConnectionState.status.