Hotfix - Unsupported Protocol Scheme in VSRM Collectors. #34
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…was getting 404.
Resolves #31
did some digging and found a couple things here..
This issue
Is caused by the vsrmclient instantiation...
restClient.HostUrl
is being set, but it should berestClientVsrm.HostUrl
.We're getting protocol error b/c the hosturl is never set for our vsrm client, meaning there's no http/https.
After fixing the above I found that in the case where I have a vanity url for my org (foobar.visualstudio.com), I still needed to hit the VSTRM endpoint directly to get release data. Removing the if statement on L117 resolves both issues.