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.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.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 - v23.14

Details of the product update v23.14 from 12th of April 2023.

IMPORTANT: New Releases Procedure

Kindly note that our release process is changing. In future, we will release updates once per month (in the last week of each month). This change increases efficiency for the development teams and should not significantly influence delivery times for feature requests. In the current process, feature requests are groomed in 1 sprint, then implemented in the following sprint. In the new process, the grooming and implementation can be executed within a single sprint.

Note: Additional releases are possible in case of any critical changes or urgent feature updates.

See compared diagram below

Releases compare

Features

“Logs” page: add step name

We added the Step Name column next to the Flow Name on the Logs page. This makes it easier to isolate relevant logs during trouble shooting.

Note: While hovering on Mapper icon the tooltip will display information with steps interaction.

Logs

Transfer modal windows to the new styles: Transform UI for “History” page to React.

We applied a new design to the History tab on the Flow-Designer page and transfer it from ember to react

History

Creating a values file for the platform chart for deploying on the secondary cluster

Special Release Procedure (if haproxy is exposed)

Firstly deploy haproxy, and only then the platform. Otherwise, some services will crash.

Helm config changes:

  1. Added .Values.global.variables.SECONDARY_PLATFORM_CLUSTERS to admiral chart in the next format 
    SECONDARY_PLATFORM_CLUSTERS:
  - name: 'secondary-cluster' # required
 credentials:
   name: 'my-user' # required
   password: 'some-password' # required
 disabled: false
 disabledRealtimeFlows: false
  2. Added ability to disable replicated admiral services .Values.global.services..enabled (default: true)
  3. Added annotation service.beta.kubernetes.io/azure-load-balancer-ipv4 to all internal load balancers if cloud provider is AZURE
  4. Added values-secondary.yaml file to admiral and platform charts for disabling services that do NOT run on secondary clusters
  5. Added ability in deploy.sh to deploy the platform to secondary cluster (i.e. using values-secondary.yaml). The command example:
KUBE_CONTEXT=great-moraq-stannis USE_SECONDARY=true ./deploy.sh deploy great-moraq

Changes required in configurations in k8s clusters (e.g. stage-clusters unmerged PR):

  1. In haproxy.yaml add expose: true and loadBalancerIp: ""

  2. In platoform.yaml:

    2.1. In global.services.api add expose: true and loadBalancerIp: ""

    2.2. In global.services.maester add expose: true and loadBalancerIp: ""

    2.3. In global.services.steward add expose: true and loadBalancerIp: ""

KUBE_CONTEXT=great-moraq-stannis USE_SECONDARY=true ./deploy.sh deploy great-moraq

Changes required in configurations in k8s clusters (e.g. stage-clusters unmerged PR):

  1. In haproxy.yaml add expose: true and loadBalancerIp: ""

  2. In platoform.yaml:

    2.1. In global.services.api add expose: true and loadBalancerIp: ""

    2.2. In global.services.maester add expose: true and loadBalancerIp: ""

    2.3. In global.services.steward add expose: true and loadBalancerIp: ""

    2.4. In global.services.pssLoadBalancer add expose: true

  3. In secrets.yaml change all occurrences of haproxy-service.platform.svc.cluster.local to an actual haproxy loadbalancer IP address

Fixed Bugs

  • FIXED bug 500 TimeoutError on GET v2/logs in case of applying together multi-filtering and search
  • FIXED bug, that causes the Websocket for thread updates makes duplicate requests for Flows and Users

Components

AMQP component 1.4.2

  • ADDED retry mechanism on connection errors
  • ADDED configuration fields to set retry options
  • ADDED Don't encrypt payload and Content-Type configuration fields to Publish action
  • ADDED Don't decrypt payload configuration field to Consume trigger
  • UPDATED the Sailor library version to 2.7.1
  • UPDATED the amqplib library version to 0.10.3
  • FIXED bug where the component has cloned connections in Publish action
  • FIXED issue with the shutdown hook in Consume trigger

Splitter component 1.4.4

  • FIXED bug while asynchronous polling with Splitter in Re-assemble Messages mode

Jira Cloud component 1.1.0

  • ADDED Lookup Object (at most one) Action
  • ADDED Upsert Object Action