We are pleased to announce the 1.3.0.RC1 release of the Spring Cloud Data Flow and its associated ecosystem of projects.
To simplify the overall experience of opting into using Skipper to deploy streams, a feature toggle provides you the ability to switch between skipper mode and the previous 'classic' mode. The feature toggle is used in both the Shell and the Server. The default value is to use the 'classic' non-skipper mode. To enable skipper mode, pass in the following Spring Boot options.
java -jar spring-cloud-dataflow-server-local-1.3.0.RC1.jar \ --spring.cloud.dataflow.features.skipper-enabled=true java -jar spring-cloud-dataflow-shell-1.3.0.RC1.jar --dataflow.mode=skipper
This also allowed us to remove
stream skipper commands introduced in 1.3 M3 and collapse skipper behavior into
You can retrieve the deployment properties using the command
When in Skipper mode, multiple versions of a stream application can be registered. A default version is used when deploying the stream. You can set the default version using the new command
app default. When upgrading an application version in a stream, you must first register it in Data Flow.
You can restart and stop an already running batch-job as well as get more information about a stream, such as each application version and the application/deployment properties.
Added deployment property builders to help avoid typos when setting commonly used deployment properties.
The local server lets you deploy task and stream applications in debug mode so that you can attache a debugger.
Please try it out, share your feedback, and consider contributing to the project!