fides
fides copied to clipboard
ethyca
Research: Differentiate between errors based on HTTP responses
USER STORY
As an admin, I want to a be able to CRUD a list of known, acceptable http errors for each connector.
REQUIREMENTS
Is it possible to expose an allowlist/denylist of errors that should cause the entire subject request to fail? Ex: a java.net.SocketTimeoutException: Read timed out should likely cause a request to fail as it should notify someone that the connection wasn’t able to successfully send the request. Compared to a ContactPhone Not found! should likely not cause the entire subject request to fail because it’s valid that the system might not contain the subject’s phone number.
This way, we provide more tools for our customers to be able to tailor the application to fit their needs without needing us to write in some logic on which errors fidesops should/shouldn’t accept.
This would be particularly useful for the case of 422s error codes. Shopify uses this error code when they are legally in the right to NOT delete data. In that case, we shouldn’t error out the request entirely and the request should proceed.
AC
- Add a section to the configure connectors screen for Error Suppression
- Add a Suppress Error button
- On button click open a form to fill out http error details
- On Save, update their connector to suppress the error and display it in the Error Suppression Section
DESIGNS
N/A
