updates
There was a fix for sender service which was ignoring messages without TTL being set. Because of this, some campaigns with big intervals were iddling.
Other then that, there is a broadcast-interval feature that was added to the system. In order to work, it required updates across multiple services:
- manager in order to detect broadcast intervals
- directory-messages in order to work with age segments
- manager-api to provide latest database changes as well as API for broadcasts settings
- subscribers-cache in order to support new segments during it’s estimation stage
- directory-segments-observer to properly update segments
- manager-time-events new service needs to be enabled for age segments to be updated on a daily basis
update plan
- update manager API
- update directory-segments-observer
- run migrations
- start manager-time-events
- update directory-messages, manager, subscribers-cache on all prems
- run migrations
update
- go-sender [before: 1.17.8.0][after: 1.17.12.0] deployment
- manager-api [before: 1.99.3.6][after: 1.102.15.1] deployment
- manager [before: 1.99.3.1][after: 1.102.15.1] deployment
- directory-segments-observer [before: 1.44.16.6][after: 1.78.0.1] deployment
- directory-server [before: 1.69.2.1][after: 1.78.0.1] deployment
- directory-messages [before: 1.75.13.1][after: 1.78.0.1] deployment
- subscribers-cache [before: 1.69.2.1][after: 1.78.0.1] deployment
- manager-time-events [before: 1.102.15.1][after: 1.102.15.1] deployment
deployment render all [[templates/items/deployment]] where page = @page.name