File-based-service-bindings: improved errors #4693
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
philippthun
changed the title
jochenehret
reviewed
Dec 2, 2025
The ServiceBindingFilesBuilder can raise an IncompatibleBindings exception in case of entries violating the specification for file names or if the overall file size is too big. When pushing an app these errors were shown as StagerErrors (with the correct error message); for other operations - i.e. restart, restage - an UnknownError was returned. This change ensures that in any case an UnprocessableEntity (ApiError) is returned (with the concrete error message).
Switching from service-binding-k8s to file-based-vcap-services via manifest entries (features) raised an error. This change fixes the wrong validation for this corner case.
philippthun
force-pushed
the
file-based-service-bindings-improved-errors
branch
from
41fbc23 to
00fa649
Compare
jochenehret
approved these changes
Dec 8, 2025
ari-wg-gitbot
added a commit
to cloudfoundry/capi-release
that referenced
this pull request
Dec 8, 2025
Changes in cloud_controller_ng:
- File-based-service-bindings: improved errors
PR: cloudfoundry/cloud_controller_ng#4693
Author: Philipp Thun <[email protected]>
sethboyles
pushed a commit
to atanas-attodorov-wq/cloud_controller_ng
that referenced
this pull request
Dec 11, 2025
* Convert IncompatibleBindings error to UnprocessableEntity (ApiError) The ServiceBindingFilesBuilder can raise an IncompatibleBindings exception in case of entries violating the specification for file names or if the overall file size is too big. When pushing an app these errors were shown as StagerErrors (with the correct error message); for other operations - i.e. restart, restage - an UnknownError was returned. This change ensures that in any case an UnprocessableEntity (ApiError) is returned (with the concrete error message). * Fix validation of conflicting manifest features Switching from service-binding-k8s to file-based-vcap-services via manifest entries (features) raised an error. This change fixes the wrong validation for this corner case.
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.
IncompatibleBindingserror toUnprocessableEntity(ApiError)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