Jump to
Product Updates
v24.45 v24.40 v24.36 v24.27 v24.23 v24.17 v24.13 v24.09 v24.05 v24.01 v23.48 v23.44 v23.39 v23.31 v23.27 v23.27.1 v23.24 v23.19 v23.19.1 v23.14 v23.14.1 v23.12 v23.10 v23.08 v23.06 v23.04 v23.02 v22.52 v22.50 v22.48 v22.46 v22.44 v22.42 v22.38 v22.36 v22.34 v22.32 v22.30 v22.28 v22.26 v22.24 v22.22 v22.20 v22.18.1 v22.16 v22.14 v22.12 v22.10 v22.08 v22.06 v22.04 v22.02 v21.51 v21.49 v21.47 v21.45 v21.43 v21.41 v21.39 v21.37 v21.35 v21.33 v21.31 v21.27 v21.23 v21.19 v21.14 v21.10 v21.06 v21.02 v20.51 v20.47 v20.43 v20.39 v20.35 v20.31 v20.27 v20.23 v20.19 v20.15 v20.11 v20.07 v20.03
Updated on

Product Update - v22.40

Details of the product update v22.40 from 6th of October 2022.

Improvements

Developer Teams: New design & improved functionality

We continue to update our User Interface to improve ease of use. This time it is the UI surrounding Developer Teams that is updated. When you navigate to Development > Developer Teams you will notice new uniform design:

Developer Teams: New design

Along with the new design we added a functionality to delete the developer team using the User Interface. Previously this functionality was only available via an API call.

Please Note: You can only delete a Developer Team when it contains no respoitories. The platform will give an error if you attempt to delete it when there is even one repository.

Updates

Java Sailor version 3.5.0

A new version of Java Sailor library 3.5.0 is released. This update adds support for Java 17.

HELM3

We constantly improve different aspects of HELM3 deployments in collaboration with our partners. This section lists updates and improvements included in this release.

Helm chart: Cron job resources defined

Platform has number of cron jobs performing different functions. With this release we added kubernetes resource definition for:

  • gendry
  • wiper conrjobs
  • git-receiver cronjobs
  • maester cronjobs
  • lookout cornjobs

Information in this section is intended for our customers who use the OEM version of the elastic.io platform.

Force pull/push for externally built docker components

In this update of our automatic component delivery feature we introduce a new API endpoint to force pull of a component version from external docker registry: POST /v2/components/:component_id/docker-pull/:version. This endpoint forces pull of a component version from external docker registry. The component must belong to one of the user’s team which supports the docker registry.

Executions details loading and Clickhouse

To streamline the proper data replication between Clickhouse cluster and reduce internal efforts to constantly update the Clickhouse-mongo dictionaries with every update of Clickhouse version we performed the following changes:

  • The User Interface (frontend) will load flow and user names directly from the MongoDB, instead of the bran service.
  • Removed the Clickhouse-mongo dictionaries and all related resources. Our OEM customers can delete mongo dictionary from clickhouse instances and mongodb proxy from HA-Proxy.

Please Note: as a regular user of the platform you don’t need to do anything. You will not notice any difference. This change is for customer who run a version of of the platform on their premises.

Components

Shopware 6 component 1.1.1

  • FIXED sample retrieving in some actions
  • IMPROVED Error handling in Get New and Updated Objects Polling Trigger

Microsoft Dynamics CRM v2 component 1.1.0

  • ADDED Get New and Updated Objects Polling Trigger
  • ADDED Lookup Objects (plural) Action
  • ADDED Lookup Object (at most one) Action
  • ADDED Delete Object By ID Action
  • ADDED Extract Raw System Metadata Action

REST API v2 component 2.0.14

  • UPDATED to use sailor-nodejs version 2.6.29

Microsoft Dynamics CRM

  • COMPONENT HAS BEEN DEPRECATED

Updates to multiple components

  • UPDATED the sailor library to version 2.6.29
  • FIXED the vulnerabilities in dependencies
  • ADDED new headers User-Agent and x-request-id

For the following components: