Add routable field to process stats examples#4962
Merged
Conversation
jochenehret
approved these changes
Mar 24, 2026
ari-wg-gitbot
added a commit
to cloudfoundry/capi-release
that referenced
this pull request
Mar 25, 2026
Changes in cloud_controller_ng:
- Replace Tomcat with Spring Boot
PR: cloudfoundry/cloud_controller_ng#4963
Author: Johannes Haass <johannes.haass@sap.com>
- Add routable field to process stats examples
PR: cloudfoundry/cloud_controller_ng#4962
Author: Katharina Przybill <30441792+kathap@users.noreply.github.com>
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 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.
A short explanation of the proposed change:
Add the missing routable field to the process stats JSON examples in the API documentation.
An explanation of the use cases your change solves
The routable field is documented in the process stats object specification but was missing from the JSON response examples. This inconsistency could confuse
API consumers who reference the examples when building integrations. Adding the field to the examples ensures developers see the complete response structure,
including the routable boolean that indicates whether an instance can receive traffic based on its readiness check status.
Links to any other associated PRs
I have reviewed the contributing guide
I have viewed, signed, and submitted the Contributor License Agreement
I have made this pull request to the
mainbranchI have run all the unit tests using
bundle exec rakeI have run CF Acceptance Tests