A feature was recently introduced that enables users to ignore/bypass ADM validation errors. Bypass rules are currently invoked at runtime using a JSON file. They are stored in a MongoDB collection called validationbypassrules. By default, app/lib/default-bypass-rules.json is used. Users can specify their own bypass rules by creating their own JSON file and pointing to it either via environment variable WB_REST_STATIC_BYPASS_RULES_PATH or by setting configurationFiles.staticBypassRulesPath in the JSON config.
This workflow is insufficient. Users should be able to:
- Dynamically modify bypass rules without rebooting the entire application.
- Manage bypass rules from the frontend (or any authenticated REST client).
The solution is to implement a set of CRUD endpoints for managing bypass rules.
A feature was recently introduced that enables users to ignore/bypass ADM validation errors. Bypass rules are currently invoked at runtime using a JSON file. They are stored in a MongoDB collection called
validationbypassrules. By default,app/lib/default-bypass-rules.jsonis used. Users can specify their own bypass rules by creating their own JSON file and pointing to it either via environment variableWB_REST_STATIC_BYPASS_RULES_PATHor by settingconfigurationFiles.staticBypassRulesPathin the JSON config.This workflow is insufficient. Users should be able to:
The solution is to implement a set of CRUD endpoints for managing bypass rules.