This repository was archived by the owner on Apr 27, 2026. It is now read-only.
feat: add pagination to listProjectSandboxes#90
Merged
Merged
Conversation
Member
Author
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
https://linear.app/keboola/issue/AJDA-2441/sandboxes-service-run-migration-of-imageversion-size-shared
Description
Added pagination support to
ManageClient::listProjectSandboxes(). The method now follows theLinkresponse header to fetch all pages, extracting only thenextPageTokenfrom it and reconstructing the correct URL to work around a known bug in sandboxes-api where the Link header points to the wrong endpoint.Release Notes
Change Type
New feature —
listProjectSandboxesnow returns all sandboxes across all pages instead of only the first page.Justification
Required to support the migration of
imageVersion,size, andsharedfields, which needs to enumerate all sandboxes for a project reliably.Plans for Customer Communication
No customer communication needed — this is an internal API client change.
Impact Analysis
Low risk. The change is backwards-compatible; callers receive the same return type but now get a complete result set. No breaking changes or feature flags required.
Deployment Plan
Standard CI/CD continuous deployment across all stacks.
Rollback Plan
Standard git revert if issues detected post-deployment.
Post-Release Support Plan
No follow-up actions needed after release.