[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
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
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
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
-
bug frontend good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
NavigationViewItemAutomationPeer implements IInvokeProvider but never advertises the Invoke pattern Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
unoplatform/uno#24629 ·
-
agentic-workflows Needs: Triage :mag: State: In-PR
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
Type: enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
apache/arrow-adbc#4809 ·