Skip to content

Support explicit pagination in VMware collection reads - #63

Merged
rjcloudsigma merged 1 commit into
masterfrom
fix/vmware-explicit-pagination-20261017
Oct 17, 2026
Merged

rjcloudsigma merged 1 commit into
masterfrom
fix/vmware-explicit-pagination-20261017

Conversation

@rjcloudsigma

Copy link
Copy Markdown
Contributor

Scope

Add optional query_params=None to VMwareRead.list() for explicit collection pagination through the existing transport. Preserve omitted/None/empty defaults, complete response envelope and Decimal values, and composition-only surface. No automatic traversal or lifecycle expansion.

Exactly three files: reader, six synthetic offline regression tests, finite CI count 216→222. Dependencies and workflows unchanged.

Qualification

Frozen base f1543d3; accepted tree 35e9d77cf0356d847c924cac0f3edd3a2d0ad3f0; patch SHA256 0924fb4589b3ab3ac15af79713c9e6aef0b3d34b5d4104e7085d889eea6d9597. Independent SAFE review SHA256 b748f49d1a47fce096baa622aea5d501fbc64b5533ccdaf8970a4ec2cd2e8c74.
Retained native baseline regression fails; candidate focused 6 PASS/full 222 PASS. Independent bounded VMware suite 11 PASS. Current-head installed-wheel Python 3.10/3.11/3.12 hosted checks required before merge.

Limits

VMware integration remains BETA. New fixtures are synthetic; historical malformed documentation response caveat remains. No nested-schema, arbitrary-filter, live availability, whole-operation, provider or release qualification. No live cloud/resource operations. Existing holds and OTP blocker remain unchanged.

@rjcloudsigma
rjcloudsigma merged commit 38aa6a7 into master Oct 17, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant