Add Continuation Token Support For Releases #113
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 10 commits
October 2, 2024 11:35
|
|
Are you able to take a look at this please @mblaschke ? Thank you |
mblaschke
approved these changes
Feb 9, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
As the official REST API for listing releases only supports returning up to 100 results per request (even with $Top values greater than 100), the API returns a continuation token in the "x-ms-continuationtoken" response header.
https://learn.microsoft.com/en-us/rest/api/azure/devops/release/releases/list?view=azure-devops-server-rest-7.0&tabs=HTTP
This PR introduces support to loop sending GET requests to the endpoint and passing the continuation token received (if any) along in the query string parameters. For a sufficiently large time period, this raises the limit of the number of results returned from 100 to the real value.
Before:
After:
--
I'm happy to extend this functionality to other endpoints that require continuation tokens if this PR gets approval.
Also changes the case of the 3
asstatements in the dockerfile to mitigate the build warnings.