Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[BUG]Extractor pipeline getting failed at Fetch Extractor step when trying to extract definition for single API after adding tokenization to change API name in different environment

Open
#713 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
azure, powershell
Domain
api, devops

Research direction

Start with the attached run-extractor.yaml.txt and compare its Fetch Extractor step with run-publisher.yaml.txt and run-publisher-with-env.yaml.txt. Trace how the releaseFileName variable is set before the failing download in the reported PowerShell error. Done means the extractor completes and places the single API definition in a separate folder; publishing guidance for specific or new APIs should also be addressed.

Written by the indexing model from the issue text.

Description

Release version

APIOps toolkits for Azure APIM v6.0.1.1

Describe the bug

##[error]PowerShell exited with code '1'.
##[debug]Processed: ##vso[task.issue type=error;source=TaskInternal;correlationId=d02035b8-3f57-49b2-b89f-6c13ad30cdcd;]PowerShell exited with code '1'.
##[debug]Processed: ##vso[task.complete result=Failed;]PowerShell exited with code '1'.
##[debug]task result: Failed
##[error]PowerShell wrote one or more lines to the standard error stream.
##[debug]Processed: ##vso[task.issue type=error;source=TaskInternal;correlationId=d02035b8-3f57-49b2-b89f-6c13ad30cdcd;]PowerShell wrote one or more lines to the standard error stream.
##[debug]Processed: ##vso[task.complete result=Failed;]PowerShell wrote one or more lines to the standard error stream.
##[error]InvalidOperation: /home/vsts/work/temp/e9b276f0-a9d8-4f16-946d-b3477352ff95.ps1:24
Line |
24 | … om/Azure/apiops/releases/download/v6.0.1.1/$releaseFileName
_;!!Afohz …
| ~~~~~~~~~~~~~~~~~~
| The variable '$releaseFileName__' cannot be retrieved because it has not
| been set.

##[debug]Processed: ##vso[task.issue type=error;source=CustomerScript;correlationId=d02035b8-3f57-49b2-b89f-6c13ad30cdcd;]InvalidOperation: /home/vsts/work/temp/e9b276f0-a9d8-4f16-946d-b3477352ff95.ps1:24
Line |
24 | … om/Azure/apiops/releases/download/v6.0.1.1/$releaseFileName
_;!!Afohz …
| ~~~~~~~~~~~~~~~~~~
| The variable '$releaseFileName__' cannot be retrieved because it has not
| been set.

Expected behavior

It should be extracted in a separate folder

Actual behavior

at Fetch Extractor step it is getting failed and not extracting the definition also need to know steps for publishing specific APIs or new APIs only, rather than all APIs in the Azure DevOps Repos.

Reproduction Steps

run-publisher.yaml.txt
run-publisher-with-env.yaml.txt
run-extractor.yaml.txt

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.