Spring Cloud Data Flow team is pleased to announce the release of 2.8.4 and 2.9.1
Spring Cloud Data Flow team is pleased to announce the release of 2.7.1.
2.7.1 is a maintenance release fixing following issues:
- UI bug fixes
- Cloudfoundry Java Client has been updated to 4.13.0 fixing its memory leak
- Using Spring Boot 2.3.7 and Cloud Hoxton.SR9
- Spring Cloud Task updated to 2.2.5
- Dataflow server contains fixes for docker, metrics and some endpoints
- More detailed list can be found from GitHub 2.7.1
Yes, we’re going reactive!
On behalf of the team and everyone that contributed, I am pleased to announce that the first release candidate of Spring Statemachine 3.0.0 has been released and is available from our milestone repository.
Highlights of this release include:
- Relevant api’s working with statemachine now have reactive methods.
- From a functional point of view this release is equivalent what’s in
2.4.xbranches apart from reactive changes.
- We’ve chosen to align with recently released Spring Boot 2.4.1.
Spring Cloud Data Flow team is pleased to announce the release of 2.6.0.
This 2.6.0 adds usual bug fixes and the following key highlights:
Platform Support for Scheduling
Tasks scheduling now have a platform support. See Scheduling Tasks
We’re now on a new version of Java CFEnv which greatly improves user experience when there is a need to bind to user created services.
Composed Task Runner as SCDF native module
Composed Task Runner is now an integral part of SCDF itself and gets registered implicitly while the users who have the custom composed task runner can still override the native one. This enables us to integrate the composed tasks management within the context of Spring Cloud Data Flow.
This is also a good reminder what’s happening on our application space by following blog series Creating a Supplier Function and generating Spring Cloud Stream Source
Spring Cloud Data Flow team is pleased to announce the release of 2.5.1.
This release includes some bug fixes with the some of the notable changes as follows:
- DeploymentProperties parsing fixes.
- Removed behaviour for server to attempt to contact dockerhub during a start.
- Fixes to dataflow client to re-authorize when oauth client credentials are used.
- Liveness and readiness probe changes to kubernetes deployment files.
- Upgrades to
Spring Boot 2.2.7and
Spring Cloud Hoxton.SR4. New dependencies from these fixed an issue in
Spring Data Restwhich caused repository mappings DATAREST-1502 to stop working and effectively caused UI and Skipper to start behaving erratically in
Data Flow 2.5.0.
The release 2.4.0 mainly focused on the UI updates and selected enhacements. Our post for 2.4.0.M1 contains more info about the changes.
Stream Editor went through a much-needed touch of love and should now be more visually appealing. Here’s a simple screenshot what it looks like:
Support for using Maven Wagon transport for HTTP has been added to the Maven Artifact Resolver infrastructure. The driver for this was a request from a user to be able to use preemptive authentication with JFrog’s artifactory. Use of it is currently optional via a property but we’re looking to make it default sometime in the future and possibly introduce more wagon transports which might provide interesting options to place your artifacts behind ssh, git or whatever Apache Wagon is able to provide. If you have a particular interest or experience of it, let us know.
This is a maintenance release for small bug fixes, enhancements, and dependency updates. Generally speaking, we’re now on Spring Cloud Hoxton SR1. List of fixed issues can be found from 2.3.1 Issue List
Support for using Maven Wagon transport for HTTP has been added to the Maven Artifact Resolver infrastructure. The driver for this was a request from a user to be able to use preemptive authentication with JFrog’s artifactory. Use of it is currently optional via a property but we’re looking to make it default sometime in the future and possibly introduce more wagon transports which might provide interesting options to place your artifacts behind ssh, git or whatever Apache Wagon is able to provide.
The release 2.3.0 delivers a lot of enhancements and generic compatibility changes for Spring Boot 2.2.x and Spring Cloud Hoxton.
As task applications evolve faster to keep up with business needs, the ability for new versions to be consumed via Data Flow in an automated way is needed. While Data Flow has supported the ability to register multiple versions of a task application in previous iterations, the ability to run them in a practical way by re-hydrating command line arguments, deployment properties, and application properties used in previous executions has been missing. In this version, the storage of those values in a manifest and the ability to both retrieve them to determine if an application needs to be upgraded and apply them to the new execution allows for developers to create continuous deployment flows for their task applications. All these capabilities are readily available through RESTful APIs, as well, so the overall CI/CD workflow for Tasks can be automated.
I’m pleased to announce a first milestone release of a Spring Statemachine 3.0.0.M1 and with these words I can say that Statemachine is going reactive.
Statemachine itself would not need to be reactive for its own execution but as soon as machine steps outside of its controlled environment to execute user defined logic like Actions and Guards there is no guarantees that those features would not block.
Those using persisting features with a databases will benefit with reactive changes when that side of a world becomes more reactive. Essentially every time we need to take a step outside from a machine world we may hit blocking IO operations.