When deploying a stream, properties fall into two groups:
- Properties that control how the apps are deployed to the target platform and that use a
deployerprefix are referred to as deployer properties.
- Properties that control or override how the application behave and that are set during stream creation are referred to as application properties.
You need to pick a defined platform configuration where each platform type (
kubernetes) has a different set of possible deployment properties. Every platform has a set of generic properties for
disk reservations and
count to define how many instances should be created on that platform. The following image shows the Deploy Stream Definition view, where you can set these properties:
The following image shows an example of how to override the
local deployer properties (note that these properties can be defined globally or per application):
The following image shows an example of a
time application's properties:
You can switch betwewn Freetext and Builder based representation to define properties. The following image shows the Freetext editor:
Once the properties are applied, they get translated by SCDF to well-defined properties, as shown in the next listing.
Properties may have default values. If a value remains unchanged, it is removed from a derived properties list.
app.time.trigger.initial-delay=1 deployer.*.cpu=1 deployer.*.local.shutdown-timeout=60 deployer.*.memory=512 deployer.log.count=2 deployer.log.local.delete-files-on-exit=false deployer.time.disk=512 spring.cloud.dataflow.skipper.platformName=local-debug
The preceding example would be as follows in SCDF shell:
stream deploy --name ticktock --properties "app.time.trigger.initial-delay=1,deployer.*.cpu=1,deployer.*.local.shutdown-timeout=60,deployer.*.memory=512,deployer.log.count=2,deployer.log.local.delete-files-on-exit=false,deployer.time.disk=512,spring.cloud.dataflow.skipper.platformName=local-debug" Deployment request has been sent for stream 'ticktock'