-
Notifications
You must be signed in to change notification settings - Fork 319
Fixing pagination on v3._ListSecurityGroupsRequest #1277
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Kehrlann
merged 3 commits into
cloudfoundry:main
from
SaifuddinMerchant:feature/issue-1242-bug-fix-v3-ListSecurityGroupsRequest-extends-wrong-pagination-group-fix-author-email
May 15, 2025
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
1446d37
issue-1242 fixing version of PaginatedRequest implemented by v3._List…
SaifuddinMerchant 33fce00
issue-1242 running mvn spotless:apply to fix formatting for SecurityG…
SaifuddinMerchant 563d381
issue-1242 Fixes issue that the subsequent listPage is not called bec…
SaifuddinMerchant File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am unsure whether this test really showcases #1242 .
When I revert the change to have a v2 paginated request, and change the test to use
.resultsPerPage(1)
, it still passes on against CC API 3.191.0.With
.resultsPerPage(1)
, does it fail on your CF deployment?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The failure I've seen is - results-per-page is a invalid parameter for V3 API.
This matches what I expect given the specs
https://v3-apidocs.cloudfoundry.org/version/3.191.0/index.html#list-security-groups
org.cloudfoundry.client.v3.ClientV3Exception: CF-UnprocessableEntity(10008): Unknown query parameter(s): 'results-per-page'. Valid parameters are: 'page', 'per_page', 'order_by', 'created_ats', 'updated_ats', 'guids', 'names', 'running_space_guids', 'staging_space_guids', 'globally_enabled_running', 'globally_enabled_staging'
at org.cloudfoundry.reactor.util.ErrorPayloadMappers.lambda$null$2(ErrorPayloadMappers.java:62)
I haven't been able to run the integration test stand alone, but I do get the issue above using resultsPerPage(x) in my application
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Got it.
The test is incorrect, and is not testing what's intended, because when you do
This returns a
Mono<Flux<SecurityGroupResource>>
. By subscribing to this, through.verify(...)
, only thethis.securityGroup
request is ever called. The subsequent listPage is not called because nothing subscribes to theFlux
it returns.Instead, you should do:
This gives you a
Flux<SecurityGroupResource>
, and all calls are made. By doing that, I'm getting the error with the v2 pagination:Could you please update the test?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Greatly Appreciate the feedback and help, I will make the change
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm also going to try and see if I can run the actual integration test for this method on my installation, so I might take some time to do that update
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have fixed the test based on your feedback. No change from what you suggested. I can't run the integration test module but I was able to run just the specific test case with some modifications from my own module.
P.S I had based my test case on
public void list()
that I think suffers from a similar issue aka the listSecurityGroup is never called.