We would like to inform you all about the impending roll-out of the new Integration flow Step configuration page during our next 22.06 release (10th of February 2022). Our OEM customers will receive the detailed explanation of changes in advance.
Here is the difference of already configured integration step showing the summary page:
We would like to draw your attention to the impending changes:
Next screenshot shows details of a component configuration view where not all sections are completed:
Here you can see the difference between already configured sections (shown in green), next section to configure (filled grey) and the other sections (hollow grey) which will not be possible to configure unless the previous section is completed.
Next screenshot shows details of a component configuration view where the Jsonata field has an incorrect entry:
The release 22.04 includes lot’s of work under the hood. Our team is working to improve and refactor some of the core microservices.
In our 22.02 release view announced our intention to find a new path for component deployments. The one which would not require direct involvement of our support.
With this release we are happy to let you know that we have made significant progress in identifying the reliable mechanism and testing our first node.js and Java component deployments using the automated build processes from CircleCI.
Here is the workflow we have already in place:
tag) is created in the GitHub component repository and the release is published.
tagversion and submitted into the Dockerhub.
latestversion is created at Dockerhub side each time code is updated.
Stay tuned for our next steps.
News in this section are for our customers who use OEM version of the elastic.io platform.
In the release 21.45 we announced about the new quota feature capability to
limit flow counts per
tenant. To apply this quota
you must have either the Service Account or Quota Manager credentials.
We have now a dedicated documentation page about the Flow Count Limit.
Lookup Object by IDaction
Lookup Objects by multiple filtersaction
Make Raw Requestaction
Create JSON Patchaction
Apply JSON Patchaction