Skip to content

21.0.0
Compare
Choose a tag to compare
@weberjm weberjm released this 04 Mar 14:17
· 1221 commits to master since this release
v21.0.0
1dfabc8
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
⭐ See below for information on using release images in deployment

Features

ID Linking

We made multiple changes to enable linking of IDs across connected system to ensure that data records can be updated. Read more.

Orchestrator Replication

Added basic support for replicating the Component Orchestrator inside of the Kubernetes cluster. This included adding a new "preparing" state for Flows while initializing. Future releases will focus on improving the performance and scalability of replicated Orchestrators.

Enhancements

  • Made preparations for upcoming new services (e.g. Raw Data Storage)
  • Changed the message format used in multiple services as part of ongoing work described in #1078
  • Updated event bus lib for better handling of service and component messages
  • Updated service/lib test setup and packages
  • Upon login, a User's record will no longer be marked as updated. (safeguard.lastLogin will be updated, but updatedAt will not be modifed)
  • Connector transforms are now supported via Flow Configuration, and can be sent via the nodeSettings object

Fixes

  • Removed race condition while starting and stopping local components in a replicated orchestrator setup
  • Fixed problem in components where they could mistakenly think their publishChannel is full and wait perpetually for a "drain" event (#1139)
  • Fixed some memory leaks caused by older versions of mongoose (#1186)
  • Corrected problems in Scheduler Deployments

Other

Documentation Restructuring

Our documentation page has been restructured to make it easier to find information. We also worked on updating the content and will invest more time on documentation in the future. Please give us feedback and contribute if you find errors or have requests for more documentation on specific topics.

Release Image Versioning

Upon release, the appropriate Docker Hub versions of all Framework Services will be tagged with the release version. Deployments can then use the release version to ensure interoperability of service capabilities.

Assets 2