DSS allows us to programmatically develop API endpoints logic.
The logic consists of plain Python/R code, with simple responses (primitive values or JSON) and doesn't currently offer a wait of customizing the HTTP status to of this response for consumers.
While integrating with other microservices in an enterprise environment, as a very standardized good practice, these consumers expect HTTP statuses that properly indicated what happened (ref: https://httpstatuses.com/😞
200 - Everything ran just fine
500 - Some internal error occurred (e.g. some error in the API developed in DSS or some unavailability of API Node)
4xx - A range o possible error codes that indicate specific errors as expected errors/validations which indicate that the consumer needs to fix something.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.