JamesProant
JamesProant
Hi @jeroenmaes thanks for the feedback. I am also using Azure DevOps and a Linux Agent. What I guess might be causing the issue on Windows is possibly the file...
Just wanted to give an update on a small change I made to the script. I added a .Trim() and .ToLower() to the versionSetName and the displayName, so that the...
Hi @waelkdouh , I have tested with version 6.0.1 but I don't see any version set filtering happening. If I extract an API then I still get every version set...
@guythetechie thanks for the response. Our main concern when raising this issue is that we are not receiving the product artifacts as described in the subfolder structure in the release...
@guythetechie any update on this?
Hi @guythetechie thanks for the response, no worries on the delay. The configuration.extractor.yaml looks like this: ```yaml apiNames: - apiA productNames: - apiProduct ``` The product and API are both...
@guythetechie any updates on this issue?
@v-dast The error is indicating that the variable **$releaseFileName** is not being set. Normally it is set right before the "Downloading release" step: ```ps Write-Information "Setting name variables..." $releaseFileName =...
> Need help with extracting a single API and Publishing that single API only to higher environment instead of all APIs in azure DevOps repos This is a different issue....
@christopherhouse We ran into the same issue and solved the problem with this ps script below which you can add after the "run extractor" task in the run-extractor.yaml file: ```ps...