[BUG] Not able to extract a versioned api

Open
#875 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Active
Tech stack
azure, csharp
Domain
api, devops

Research direction

Start with the config.extractor.yaml example and reproduce the empty artifact using an API version identified by a v1 URL path. Compare the versioned API extraction behavior with versionset extraction and deployment, including whether a Versionset must be created separately. Done means the versioned API is extracted into a non-empty artifact and the expected deployment behavior is documented or works.

Written by the indexing model from the issue text.

Description

Release version

Not able to extract a versioned api

Describe the bug

I use config.extractor.yaml as below but nothing shows up in output, How to extract and deploy versioned api?
apiNames:
-orders-api-v1.
versionssetName

  • orders-api
Expected behavior

It should work same as versions api extraction and deployment. Is deployment extra too to create a Versionset ?

Actual behavior

Nothing gets extracted i get an empty artifact .

Reproduction Steps

Create a version to an API as URL path version identifier v1. and then add extract apiname as as Name in v1 version

Dominant language
C#
Stars
448
Forks
247
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Azure/apiops

All issues in Azure/apiops

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.