Logstash from stack catalog get corrupted config

I tried to set up a ELK stack with logsprout from the stack catalog. Logstash collector won’t start and receive logs. If i view the configuration on the logstash stack i notice that the input have been corrupted. When i started the stack i used the default config that was all ready filled in. Is this a bug? I’m using using the latest Rancher ( installed yesterday )

logstash-indexer-config:
  scale: 1
  metadata: &id002
    io.rancher.service.hash: 26e9efc7fd608e06eb1c19e98fdf3439d5c8ab48
    logstash:
      filters: |2+

      inputs: |
        redis {
          host => "redis"
          port => "6379"
          data_type => "list"
          key => "logstash"
        }
      outputs: "elasticsearch {\n  host \n"
redis:
  scale: 1
  metadata:
    io.rancher.service.hash: ca4e0e00b4af4d172ff3b94c8f0d631fb1670c50
logstash-collector-config:
  scale: 1
  metadata: &id001
    io.rancher.service.hash: 2fe66e36ba015985cc86e1b877ed3427d7442de4
    logstash:
      inputs: "udp {\n  port \n"
      outputs: |
        redis {
          host => "redis"
          port => "6379"
          data_type => "list"
          key => "logstash"
        }
logstash-collector:
  scale: 1
  metadata: *id001
logstash-indexer:
  scale: 1
  metadata: *id002

Hmm… this was seen in pre-released versions of the catalog where rancher-compose would fail if the variables had equal signs. Looks like we have a bug thats returned. Will open a github issue… sorry for the inconvenience.