Event log has been moved to separate database.

Breaking changes

Event log has been moved to separate database and this requires new configuration options to /etc/oneportal/oneportal.conf

mongo.log.addr=mongodb://localhost:28017/?replicaSet=oneportal
mongo.log.dbname=oneportal_log
mongo.log.writeconcern=W1
mongo.log.readpreference=NEAREST

If these new configuration options are not specified, backwards compatibility mode is used and event logs will use oneportal_aux database (previous default).

Additionally, database configuration now recommends full MongoDB URIs for database address, including possible replica set name. If database does not have replica set defined (standalone mongodb), it should be excluded from MongoDB URI. By default, backwards compatibility exists but it only works when MongoDB has replica set with name oneportal.

Recommended database configuration with replica set:

mongo.addr=mongodb://localhost:28017/?replicaSet=oneportal

Recommended database configuration for standalone MongoDB:

mongo.addr=mongodb://localhost:28017

New features

• [JIRA-1] Short description of new feature. If necessary, link to additional documentation (only if truly useful, don’t overwhelm the reader) or describe how the reader can get started using it.

• [JIRA-2, JIRA-3] Include a reference to the related Jira issue(s) so that you and others can quickly find out what you are writing about, in case you are not making much sense.

Improvements

• [JIRA-4] Short description of improvement. These are likely just one-liners.

Bug fixes

• [JIRA-5] Short description of original issue. If fix requires post-install user actions, describe here.

TIS v3.x.y (released 00-Mon-2021)

Bug fixes

• patch releases are mostly bug fixes. list all issues from jira here.