Unable to extract Operations for an API, while running extractor pipeline

Open
#751 4 comments 0 reactions 1 assignee View on GitHub

@guythetechie is already working on this.

Since Apr 22, 2025.

Assessment

This issue has not been assessed yet.

Description

Release version

v4.1.3

Describe the bug

Hi Team,

We are using APIOps pipelines to extract and deploy the APIs from One environment to another in APIM instance.

When trying to run the API extract pipeline, the APIs are being extracted but the operations inside an API are not extracting.

The operations are only extracted when we manually go inside one of the api operation and edit and save it. We want to understand this behaviour why it is happening like this.

Image

One more thing we observed is, as shown in above image, it is not able to extract operations , if service URL in the backend policies is not Overridden. If the service URL in the backend policy is overridden with some value, it is able to extract those Operations, which is strange. Want to understand this behaviour.

Currently we are using apios version v4.1.3 in the pipelines for extracting apis from APIM.

I tried with different versions like 4.6.0 , 5.0.1 , 5.1.4 , 6.0.1.

For 4.6.0 and 5.0.1 versions , the pipeline is able to fetch apis, but still the issue is there while fetching operations inside an API.

For latest versions like 5.1.4 , 6.0.1 and other 6.0+ versions, while fetching extractor itself the pipeline is failing .

Regards,
Mallikarjun

Expected behavior

Need to extract all the operations inside an API

Actual behavior

When trying to run the API extract pipeline, the APIs are being extracted but the operations inside an API are not extracting.

Reproduction Steps
  1. While running the extractor pipeline, it is able to extract the APIs, but unable to extract the operations inside it.
Dominant language
C#
Stars
448
Forks
247
PR merge metrics
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.