Get ahead
VMware offers training and certification to turbo-charge your progress.
Learn moreThe Spring Cloud Data Flow team is pleased to announce the release of 1.5.0 M1
. Follow the Getting Started guides for Local Server, Cloud Foundry, and Kubernetes.
Here are the highlights:
UI Improvements
Spring Boot & Spring Cloud Stream 2.0 Support
Nested splits for Composed Tasks
Metrics Collector 2.0 M1
Stream Application Starters Darwin M1 release train
Support for deploying to multiple Kubernetes clusters
We have continued to improve the UI/UX of the Dashboard. You will immediately notice an overall lighter weight design. The Tasks tab has been rewritten to match the UX styling of the other tabs. The stream-builder view includes many optimizations ranging from better form validation and eager error reporting. Try it out!
There has also been a significant amount of refactoring to optimize the codebase and prepare for future extensions and feature additions.
We now support deploying Spring Boot and Spring Cloud Stream 2.0 based applications. A small utility class in the Spring Cloud Stream Application Starters library adds Micrometer metric tags to help identify the streams and applications in the desired monitoring backend.
Due to popular demand, this release added DSL support to interpret “nested splits” in composed tasks. The Flo Dashboard and Shell tooling automatically adapt to nested splits.
Here is how it looks in the Flo Dashboard for the DSL expression:
<<extractFromFTP && cleanseFiles || extractFromS3 && splitTransform> && merge || extractfromOracle>
To use this feature, you’d have to register the 1.1.1.BUILD-SNAPSHOT
version of the Composed Task Runner in SCDF.
For Maven users
maven://org.springframework.cloud.task.app:composedtaskrunner-task:1.1.1.BUILD-SNAPSHOT
and for Docker users
docker:springcloudtask/composedtaskrunner-task:latest
The 2.0 M1 release of Metrics Collector is based on Spring Boot 2.0 and Spring Cloud Stream 2.0. The Metrics Collector server supports collecting metrics from streams that contain only Boot 1.x or 2.x apps as well as streams that contain a mixture of Boot versions. A consistent representation of the throughput rates will be captured and propagated over to SCDF’s Dashboard. A sample demonstrating comprehensive metrics support with the help of Micrometer and a few of the supported backends are in the works - stay tuned!
The release train Darwin updates the application starters to be based on Spring Boot & Spring Cloud Stream 2.0. A gRPC processor has been added. Import URL can be found here.
While using Skipper with Data Flow, it is already possible to target application deployment to multiple platform backends. However, we did not support targeting multiple Kubernetes platforms. Now you can. :)
A growing number of new issues dealt with the ability to individually and globally override JAVA_OPTS
for applications running on Cloud Foundry. We added a deployer property, e.g. deployer.yourapp.cloudfoundry.javaOpts
to support setting this specific environment variable.
The Kubernetes server now supports using a private Docker registry on a per-application basis.
As always, we welcome feedback and contributions, so please reach out to us on Stackoverflow or GitHub or via Gitter.
Please try it out, share your feedback, and consider contributing to the project!