julian.baeume authored 1 year ago and julian.baeume committed 1 year ago

Changelog:
- introduce two separate roles for middleware deployments:
    - ui-middleware: read from redis only, listen to version updates, can easily be scaled
    - updater: split out all code that writes to redis, no need to scale > 1

- Unit and Integration tests now use "inject" instead of starting a server
  and using supertest.
- Add Coverage Reports and "test:dev" mode. This enables a mocha --watch
  like workflow using nodemon, as --watch does not work with esm modules.
- Reorganized and renamed files and functions

Set cache control to no-store. The ui-middleware will then only look at the remote servers for the files and never in the local cache

Do not accept updates when the ui-containers are not available

this should help to get insights about how the caches are filled locally

This commit contains a fixup for the original commit 64f2780a

richard.petersen authored 2 years ago and richard.petersen committed 2 years ago

Only warn, when meta.json is missing since the ui-middleware will fall back to a computed hash value

alexander.quast authored 2 years ago and richard.petersen committed 2 years ago

Changelog:
 - Changed all 'trace' logs to level 'debug'
 - Added logging to the version check functions on log level 'info' and 'debug'
 - Added some time measures on ready checks to see what's taking so long on startup

Root cause: configuration was only reloaded on those nodes, that did the version update. The other nodes might not notice that.
Solution: On propagated version changes, the nodes always check for config changes