I'm confused as to what you're trying to do. If you need to run SCDF + Skipper on CF, have you followed the getting-started guide in entirety? See here.
Both Skipper and SCDF are 2 different apps. They need 2 different
manifest.yml with the respective properties as described in the docs ^^.
Also: SCDF uses Skipper APIs behind the scenes. You need to
cf push Skipper and provide the route of Skipper to SCDF via
Yes, you can. You'd separate each application-specific properties by:
, (comma is the delimiter). Alternatively, you can also use the
--propertiesFile option to supply a file with "n" number of properties for each application.
Lastly, for SCDF questions, please use https://gitter.im/spring-cloud/spring-cloud-dataflow channel going forward.
Hi, @cezannetx03_twitter. Here's some relevant info (for k8s) as to how the decision is made.
Skipper is looking to see if the health endpoint of the Boot application is OK. The spring.cloud.skipper.server.strategies.healthcheck.timeoutInMillis property sets the maximum time the upgrade process waits for a healthy app. The default value is 5 minutes. Skipper fails the deployment if it is not healthy within that time. The spring.cloud.skipper.server.strategies.healthcheck.sleepInMillis property sets how long to sleep between health checks.
More details is in the ref. guide. A similar strategy is also applied for CF and Local implementations as well.