-
Task
-
Resolution: Done
-
Major
-
None
-
None
-
None
-
False
-
-
False
-
MGDOBR - Sprint 220
Issue Description: When creating a processor calling POST /api/v1/bridges/{bridgeId}/processors with invalid configuration parameters for source or action, the endpoint returns a 400 error with the following response (missing topic param example):
{
"exception": null,
"propertyViolations": [],
"classViolations": [],
"parameterViolations": [
{
"constraintType": "PARAMETER",
"path": "addProcessorToBridge.processorRequest",
"message": "The supplied topic parameter is not valid",
"value": "com.redhat.service.smartevents.manager.api.models.requests.ProcessorRequest@6e6392bb"
},
],
"returnValueViolations": []
}
This type of error occurs when a parameter is missing, when the parameter type is URL but he provided value is not an URL, or when the provided URL parameter is not using http or https protocols.
Acceptance Criteria: The error response should be in the proper format, with id, reason etc. Like this example error for an invalid processor name:
{
"kind": "Error",
"id": "1",
"href": "/api/v1/errors/1",
"code": "OPENBRIDGE-1",
"reason": "Processor with name 'test name' already exists for bridge with id '22013906-f9d6-4e8f-898b-07bc04311449' for customer '53160135'"
}
Out of Scope: -
Additional Information: -
