Unable to extract Operations for an API, while running extractor pipeline
@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.
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
- 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
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 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
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Similar issues
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
t/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
ci-failure-cause test-failure
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area:auth FE mvp P3
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
klasolsson81/jobbliggaren#1788 ·