[BUG] API suffix not allowed to duplicate for version sets
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
No source file or test is named. Start by reproducing the migration with two API versions in the same version set and the same API suffix, then trace the APIops deployment path that creates the API. Done means the migration succeeds without the duplicate-path validation error and existing behavior remains covered by tests.
Written by the indexing model from the issue text.
Description
Release version
v6.0.2-alpha.1.0.2
Describe the bug
APIs have same API suffix of versions, it throws an error
##[error]System.Net.Http.HttpRequestException: HTTP request to URI https://management.azure.com/subscriptions/*********resourceGroups/Resource-group/providers/Microsoft.ApiManagement/service/APIM/apis/APIr-v2;rev=2?api-version=2023-09-01-preview failed with status code 400. Content is '{"error":{"code":"ValidationError","message":"One or more fields contain incorrect values:","details":[{"code":"ValidationError","target":"path","message":"Cannot create API 'API-v2' with the same Path 'glb/supplier' as API 'API-v03' unless it's a part of the same version set"}]}}'.
Expected behavior
I can manually create new version of API in the same version set with same API suffix which is not possible via APIops
Actual behavior
APIops throws an error, not allowing to create API version sets with same API suffix
Reproduction Steps
- Create an API in API management
- create version 1 and 2 with same API suffix
- Migrate API via APIops
- Dominant language
- C#
- Stars
- 448
- Forks
- 247
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Azure/apiops
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 3/5 1-2 days Newbie friendliness 70/100
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
Similar issues
-
Documentation
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
cake-build/cake#5024 ·
-
Frontend status/draft TechnicalDebt
Difficulty 2/5 1-2 days Newbie friendliness 75/100
Altinn/altinn-auth#4143 ·
-
.NET Flaky Test Testing Tests
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
getsentry/sentry-dotnet#5617 · 1 comment ·
-
:watch: Not Triaged dotnet-fsharp/svc
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
Client customer-reported needs-team-attention question Service Attention WebPubSub
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Azure/azure-sdk-for-net#63292 · 3 comments · 1 reaction ·