spring.cloud.dataflow.server.urias discussed here: https://docs.spring.io/spring-cloud-dataflow/docs/current/reference/htmlsingle/#_configuring_the_composed_task_runner_2 ?
composed-task-argumentsargument. This option will allow you to specify the command line arguments that will be passed to all the child applications of a CTR execution. i.e.
--composed-task-arguments=“foo=bar --baz=boo”will set the command line args for all child apps to
@venkatasreekanth: As far as the app coordinates are lined-up in the format as described here: https://docs.spring.io/spring-cloud-dataflow/docs/2.2.0.RELEASE/reference/htmlsingle/#_bulk_import_of_applications, you can point to the property file both from the Shell and the UI to import them into SCDF's App Registry.
You can use any of the bulk import files that we ship for the out-of-the-box apps for reference also. Example: https://dataflow.spring.io/kafka-maven-latest
--composed-task-arguments=“foo=bar --baz=boo”did not pass through either and caused a strange split on the space within the composed task arguments.
--composed-task-arguments=“--foo=bar,--baz=boo”(NB: no space either side of the comma) which perfectly passed through the arguments to the child arguments as well as allowing the configuration bindings to work where we were using a conditional property for our dependency injection.
java.lang.IllegalArgumentException: No platforms configured at org.springframework.cloud.dataflow.server.stream.SkipperStreamDeployer.determinePlatformName(SkipperStreamDeployer.java:285) at org.springframework.cloud.dataflow.server.stream.SkipperStreamDeployer.deployStream(SkipperStreamDeployer.java:220)
kubectl describe <pod-name>output, so we can verify whether the
defaultplatform is configured correctly.
This happens when there is an app that uses the following annotation.
Content-Type=application/json only appears in the
MessageHeader when deployed via SCDF. (Does not appear when it is launched manually in console)