Cafienne Engine Release 1.1.2
Platform Health Information
The Cafienne Engine has added 2 new end points
/healthreturning the full health information of the engine/versionreturning the version information of the engine
Furthermore all endpoints but above one will return HTTP 503 Service Unavailable if the health is not 100% green.
Better recovery from failing database connections
If the event journal database is not reachable, the engine now tries to restart the connection.
New Logging features with Docker
Engine logging in Docker can be enabled with a custom logback.xml.
This also enables dynamically changing the log-levels of the Case Engine.
The getting-started repository has a sample logback.xml file that writes log information both to disk (with a rolling appender that keeps the logs for 10 days).
Bootstrap tenant configuration
It is now possible to create a tenant with owners and users during startup of the Case Engine. From the local.conf file, a reference can be made to a separate configuration file that holds the tenant information. It is not possible to update the tenant setup through this mechanism. If the tenant already exists, the content of the file will be ignored.
Housekeeping
- Some internal refactoring to cleanup code and make reading configuration settings more explicit.
- If a user is only member of a single tenant, that will automatically be the default tenant for that user.
- More clear error messages if something fails in the PDF report generation component.