Azure / Azure/azure-rest-api-specs

[BUG] `x-ms-parameter-location` should be `method` for `ascLocation` in JIT network access policies

Open
#10,990 1 comment 0 reactions 0 assignees View on GitHub
Security Service Attention Swagger Cleanup
Dominant language
TypeSpec
Stars
3.1k
Forks
5.9k
Avg merge
2d 22h
Merged PRs (30d)
444

Description

- Field schema: https://github.com/Azure/azure-rest-api-specs/blob/c1c45178f4a761b48f1778ac46cdd3304d7e33ef/specification/security/resource-manager/common/v1/types.json#L337

- What happened?
All the Jit Network Access Policies REST endpoints expect ascLocation as a path parameter (see https://docs.microsoft.com/en-us/rest/api/securitycenter/jitnetworkaccesspolicies). The problem with the generated client is that ascLocation cannot be passed when calling the corresponding CRUD functions. Instead, the ascLocation is taken from the client properties.

- What did you expect or want to happen?
The property `x-ms-parameter-location` should be `method` (same as resourceGroupName or jitNetworkAccessPolicyName).

Contributor guide

Open the contributing guide

Research direction

Open specification/security/resource-manager/common/v1/types.json at line 337 and inspect the ascLocation schema alongside resourceGroupName and jitNetworkAccessPolicyName. Confirm the generated CRUD operations currently take ascLocation from client properties, then update the parameter-location metadata and validate the REST specification or generated-client behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
json, openapi
Domain
api
Issue type
Bug
Difficulty
1/5
Estimated time
Under an hour
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.