Bring domains and isolation segments to parity with the v3 reference … - #5443
Merged
Conversation
…docs
Adds permitted roles to all 15 operations with their v3 qualifiers, the
enforce_route_policies and route_policies_scope domain fields, explicit
organization and shared_organizations relationships in place of an opaque
Relationships ref, and the missing filters on the org-scoped domain list
and the isolation segment organizations list.
Language derived from:
docs/v3/source/includes/resources/domains/
docs/v3/source/includes/resources/isolation_segments/
docs/v3/source/includes/api_resources/_domains.erb
docs/v3/source/includes/api_resources/_isolation_segments.erb
Also fixes:
- The share-a-domain response schema had `items` mis-indented as a sibling
of `data`, so the schema was malformed, and its request description was
copy-pasted from isolation segments.
- The isolation segment PATCH example contained literal ERB
(`name: <%= name %>`).
- page/per_page removed from the two relationship endpoints, which accept
no query parameters and return an unpaginated relationship.
- created_ats/updated_ats added to GET /v3/organizations/{guid}/domains:
undocumented in v3, but the controller reuses DomainsListMessage.
- PATCH /v3/domains/{guid} now references the orphaned
DomainUpdateRequestBody.
ai-assisted=yes
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Samze
approved these changes
Sep 11, 2026
ari-wg-gitbot
added a commit
to cloudfoundry/capi-release
that referenced
this pull request
Sep 11, 2026
Changes in cloud_controller_ng:
- Bring domains and isolation segments to parity with the v3 reference docs
PR: cloudfoundry/cloud_controller_ng#5443
Author: Seth Boyles <seth.boyles@broadcom.com>
Author: Claude Sonnet 5 <noreply@anthropic.com>
- Add the Route Policies resource to the OpenAPI spec
PR: cloudfoundry/cloud_controller_ng#5444
Author: Seth Boyles <seth.boyles@broadcom.com>
Author: Claude Sonnet 5 <noreply@anthropic.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
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.
…docs
Adds permitted roles to all 15 operations with their v3 qualifiers, the enforce_route_policies and route_policies_scope domain fields, explicit organization and shared_organizations relationships in place of an opaque Relationships ref, and the missing filters on the org-scoped domain list and the isolation segment organizations list.
Language derived from:
docs/v3/source/includes/resources/domains/
docs/v3/source/includes/resources/isolation_segments/
docs/v3/source/includes/api_resources/_domains.erb
docs/v3/source/includes/api_resources/_isolation_segments.erb
Also fixes:
itemsmis-indented as a sibling ofdata, so the schema was malformed, and its request description was copy-pasted from isolation segments.name: <%= name %>).ai-assisted=yes
Thanks for contributing to cloud_controller_ng. To speed up the process of reviewing your pull request please provide us with:
A short explanation of the proposed change:
An explanation of the use cases your change solves
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