Azure / Azure/azure-rest-api-specs
FluidRelay Server API location support
- Dominant language
- TypeSpec
- Stars
- 3.1k
- Forks
- 5.9k
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 424
Description
The FluidRelay Service response error when the location parameter with the value "West US 2", but success with value "westus2". this not meet the api reference by
>
location | Required, string. The location of the resource. This would be one amongst the supported Azure Geo Regions registered by the RP:West US \| East US \| North Central US \| South Central US \| West Europe \| North Europe \| East Asia \| Southeast Asia \| East US 2 \| etc. Resource Providers should ignore whitespace and capitalization when accepting geo regions. That is, "West US," "westus" and "West us" should all be acceptable for the georegion. This will greatly simplify the pattern for CLI / Powershell / SDK clients. An RP should use this to create the resource in the appropriate geo-affinity region. The geo region of a resource never changes after it is created.
-- | --
related API: https://github.com/Azure/azure-rest-api-specs/blob/main/specification/fluidrelay/resource-manager/Microsoft.FluidRelay/stable/2022-04-21/fluidrelay.json
Expect: create fluid relay server success with location value as "West US 2"
Contributor guide
Research direction
The related definition is specification/fluidrelay/resource-manager/Microsoft.FluidRelay/stable/2022-04-21/fluidrelay.json; start by reading the create-server request and its location parameter constraints. Update the API specification so the spaced, case-insensitive “West US 2” form is accepted, then verify the behavior against the linked Azure resource API reference.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- openapi
- Domain
- api, cloud
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100