anchor.diff:    `:` delimiter, etc.) although we recommend using `=` as a key-value pair delimiter
     for consistency:
   
  -[source,bash,subs=attributes]
  +[source,bash]
   ----
   stream deploy foo --propertiesFile myprops.properties
   ----
  
positive.code: 2016-06-01 09:45:12.250  INFO 79194 --- [  kafka-binder-] log.sink    : 06/01/16 09:45:12
  2016-06-01 09:45:13.251  INFO 79194 --- [  kafka-binder-] log.sink    : 06/01/16 09:45:13
  ```
  
  === Passing application properties when deploying stream
  
  When you execution `stream deploy` shell command, you can optionally provide a
  comma delimited list of key=value pairs known as `deployment properties`.
  These properties allow you to specify deployment instruction for each application
  in the stream.
  
  ==== Passing instance count as deployment property
  
  If you would like to have multiple instances of an application in the stream, you
  can include a property with the deploy command:
  
  [source,bash,subs=attributes]
  ----
  dataflow:> stream deploy --name ticktock --properties "app.time.count=3"
  ----
  
  IMPORTANT: See <<spring-cloud-dataflow-stream-app-labels>>.
  
  ==== Passing stream partition properties
  A common pattern in stream processing is to partition the data as it is streamed.
  This entails deploying multiple instances of a message consuming app and using
  content-based routing so that messages containing the identical data value(s) are
  always routed to the same app instance. You can use the Deployment Properties to
  declaratively configure a partitioning strategy to route each message to a specific
  consumer instance.
  
  See below for examples of deploying partitioned streams:
  
  
negative.code:   use the `--properties` shell option and list properties as a comma separated
    list of key=value pairs, like so:
  
  [source,bash]
  ----
  stream deploy foo
      --properties "app.transform.count=2,app.transform.producer.partitionKeyExpression=payload"
  