Deployment Properties

When deploying a stream, properties fall into two groups:

  • Properties that control how the apps are deployed to the target platform. These properties use a deployer prefix and are referred to as deployer properties.
  • Properties that set application properties or override application properties set during stream creation are referred to as application properties.

You need to pick a defined platform configuration where each platform type, local, cloudfoundry or kubernetes will have a different set of possible deployment properties. There's a set of generic properties for every platform's memory, cpu and disk reservations and count to define how many instances platform should create.

Deployment Properties Overview

Below you can see an example of how to override the local deployer properties. Also, note, these properties can be defined globally or per application.

Deployment Properties Deployer Dialog

Below you can see example of a time application properties.

Deployment Properties Application Dialog

You can switch betwewn Freetext and Builder based representation to define all needed properties.

Deployment Properties Freetext

Once when the above properties are applied, they get translated by SCDF to the well-defined properties as shown below.

Properties may have default values and if a value remains unchanged, it is removed from a derived properties list.


This above example in SCDF shell would look like.

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,"
Deployment request has been sent for stream 'ticktock'