Update list packages per app API description #4459
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
In all "list" endpoint example responses there is a common pattern: ```http HTTP/1.1 200 OK Content-Type: application/json <%= yield_content :paginated_list_of_[resource] %> ``` This pattern is broken in this case and makes it inconsistent compared to the rest of the documentation
philippthun
approved these changes
Jul 24, 2025
ari-wg-gitbot
added a commit
to cloudfoundry/capi-release
that referenced
this pull request
Jul 24, 2025
Changes in cloud_controller_ng:
- Update CF V3 API definition
PR: cloudfoundry/cloud_controller_ng#4458
Author: Rashid Rashidov <[email protected]>
- Update list packages per app API description
PR: cloudfoundry/cloud_controller_ng#4459
Author: Rashid Rashidov <[email protected]>
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.
In all "list" endpoint example responses there is a common pattern:
This pattern is broken in this case and makes it inconsistent compared to the rest of the documentation
I have reviewed the contributing guide
I have viewed, signed, and submitted the Contributor License Agreement
I have made this pull request to the
mainbranch