Skip to content

Implement RFC-0027: Add max_route_options_size BOSH property#630

Open
rkoster wants to merge 2 commits intocloudfoundry:developfrom
rkoster:rfc-0027-route-options-size-limit
Open

Implement RFC-0027: Add max_route_options_size BOSH property#630
rkoster wants to merge 2 commits intocloudfoundry:developfrom
rkoster:rfc-0027-route-options-size-limit

Conversation

@rkoster
Copy link

@rkoster rkoster commented Mar 18, 2026

Summary

Adds the cc.max_route_options_size BOSH property to support the route options size limit implemented in cloudfoundry/cloud_controller_ng#4934. The property is propagated to the worker job via the cloud_controller_internal BOSH link, consistent with how other validation limits (e.g. max_labels_per_resource, max_annotations_per_resource) are shared across CC components.

Changes

  • jobs/cloud_controller_ng/spec: Added cc.max_route_options_size property (default: 1024) and exposed it in the cloud_controller_internal link's properties list
  • jobs/cloud_controller_ng/templates/cloud_controller_ng.yml.erb: Maps the property to the CC config
  • jobs/cloud_controller_worker/templates/cloud_controller_ng.yml.erb: Consumes the property via the cloud_controller_internal link

Property

Name Default Description
cc.max_route_options_size 1024 Maximum size in bytes for serialized route options JSON. Requests exceeding this limit are rejected with HTTP 422.

Related

Adds the cc.max_route_options_size BOSH property (default: 1024 bytes)
to control the maximum allowed size of route options JSON payloads.

- Add cc.max_route_options_size property to cloud_controller_ng job spec
- Expose property via cloud_controller_internal BOSH link
- Map property into cloud_controller_ng.yml.erb for api job
- Map property into cloud_controller_ng.yml.erb for worker job (via link)
- Include git-sourced gem directories in cloud_controller_ng package spec
@rkoster rkoster force-pushed the rfc-0027-route-options-size-limit branch from a0d70cb to 99eb5b3 Compare March 18, 2026 13:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant