Azure / Azure/azure-rest-api-specs

`network`: `VirtualNetworkGatewayConnections_SetSharedKey` LRO operation should response as code `201` , not `200`

Open
#24,232 1 comment 0 reactions 0 assignees View on GitHub
Network - Virtual Network Service Attention
Dominant language
TypeSpec
Stars
3.1k
Forks
5.9k
Avg merge
3d 2h
Merged PRs (30d)
424

Description

`200` means the resource has been created/updated successfully. but this operation also returns a `azure-asyncoperation` header means it is a LRO operation. so the status code should be `201` or some sdk, [like golang/autorest](https://github.com/Azure/go-autorest/blob/be633f7b83b41fc9bd41f4e99aa8664a9fa070fb/autorest/azure/async.go#L419C13-L428), will confused on the LRO result.

![image](https://github.com/Azure/azure-rest-api-specs/assets/2633022/ca60f023-27fd-4f09-ba64-f5fa07938331)

Contributor guide

Open the contributing guide

Research direction

Start by locating the REST API specification for the network operation VirtualNetworkGatewayConnections_SetSharedKey. Inspect its long-running-operation response and the azure-asyncoperation header behavior, then verify that the documented success status is 201 rather than 200 and that the resulting specification remains valid.

Written by the indexing model from the issue text.

Assessment

Tech stack
openapi
Domain
api, cloud, networking
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.