Jump to
Product Updates
v24.50 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.40 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.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 - v21.37

Details of the product update v21.37 from 16th of September 2021.

Features

Update components in all flow steps

We introduce a new feature to help update the components in all steps of your integration flow in one go. A new button Update All Components will appear in the flow designer if your flow has steps which run on older version of the component.

Update All Components Button.

The following rules apply with this new feature:

  • The Update All Components button will appear in case when the flow draft has one or more steps using an older version of the component.
  • By clicking on this button the platform will upgrade all steps to use the latest available component version - not the latest alias.
  • If your flow has a step running an outdated component version, by clicking on the Update All Components button the system will create a new draft of this flow with an updated latest component version - not set the latest alias. You can review your flow and publish it essentially upgrading all steps.

For more information go read the article on this topic.

Try metadata tool

With the platform version 21.37 we decided to reveal one of our internal tools our team uses to render the component metadata structures to see how they would look on the platform UI. You can experiment and refine the metadata structure before committing it to your custom component code. We hope this tool will be as useful for you as for our component developer team.

Try metadata tool

To access this tool navigate to the URL APP_ADDRESS/c/CONTRACT_ID/try-component-metadata where the APP_ADDRESS is the address of the platform app https://app.elastic.io and the CONTRACT_ID is your contract ID shown in your browser address bar between /c/ and /w/ while visiting the platform UI. As of this moment there is no direct navigation link from the left-hand-side menu.

For more information go read the article on this topic.

HELM3

We are in middle of constantly improving various aspects of HELM3 deployments in collaborations with our partners. These are updates and improvements done in this round.

Secrets charts separation

In the platform release 21.37 we separated the secrets chart creation from the platform charts following the best practices guidelines of the kubernetes secrets management.

You are free to choose your method to store secrets. You must define these secrets in the kubernetes before the 21.37 platform version deployment.

Deployment after secrets separation

These instructions apply when you have previously deployed platform version and need to upgrade to the latest 21.37.

  1. Scale down the stakater-reloader to 0 instances.
  2. Delete existing secrets in the platform and tasks namespaces (kubectl delete secrets --all -n platform and kubectl delete secrets --all -n tasks).
  3. Deploy all required secrets for the platform.
  4. Deploy the 21.37 version of the platform.
  5. Delete wiper job in kubernetes kubectl -n platform delete jobs -lapp=wiper. The system will restart it.

Note: You need to do steps 1 and 2 once. The stakater-reloader will scale-up automatically during the platform installation. No need to scale it up manually.

Components

JDBC component 2.4.5

  • IMPROVED the component by opening only one connection pool per one execution and reusing it.