Add missing endpoint specs for spaces usage_summary and isolation seg… - #1048
Merged
Conversation
…ment organizations
Two endpoints exist in cloud_controller_ng routes.rb but were missing
from the OpenAPI specification:
1. GET /v3/spaces/{guid}/usage_summary - public endpoint analogous to
the already-documented GET /v3/organizations/{guid}/usage_summary.
Added path definition to Spaces.yaml and wired into openapi.yaml.
2. GET /v3/isolation_segments/{guid}/organizations - path definition
already existed in IsolationSegments.yaml but was not referenced
from openapi.yaml paths section. Added the $ref to make it visible
to spec consumers.
Made-with: Cursor
Samze
approved these changes
Apr 23, 2026
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.
…ment organizations
Two endpoints exist in cloud_controller_ng routes.rb but were missing from the OpenAPI specification:
GET /v3/spaces/{guid}/usage_summary - public endpoint analogous to the already-documented GET /v3/organizations/{guid}/usage_summary. Added path definition to Spaces.yaml and wired into openapi.yaml.
GET /v3/isolation_segments/{guid}/organizations - path definition already existed in IsolationSegments.yaml but was not referenced from openapi.yaml paths section. Added the $ref to make it visible to spec consumers.
Made-with: Cursor