Rework process service validation #265
Description
Is there an existing issue for this?
- I have searched the existing issues and added correct labels.
Please describe the feature you have in mind and explain what the current shortcomings are?
Process service used to be running without any configuration validation which was often leading to obscure crashes with confusing traceback.
A few months ago, a validation was introduced before the processor event collection loop to ensure the configuration is OK and the sync can perform.
However currently if any trouble is found, a exception is raised and the service gets interrupted.
With the potential side effect:
- The whole service might not start because of a simple configuration mistake in single project
- Service is likely to run as a docker container, accessing those logs might be hard
- Report error is not always meaningful
- It's hard to check from out from the outside if the processor started properly or not
- This validation only runs on service start, but is not enforced when the configuration changes.
Suggested implementation?
No response
Describe alternatives you've considered:
No response