Comment 0 for bug 1938807

Hi,

As of mitaka the pipeline-yaml configuration option does not work, and therefore users/customers are not able to specify their own customised pipeline.

A new option was added to add remote-sink, which allowed to add multiple remote sinks to the configuration.

I am proposing 2 things

1. Update the config.yaml to update the pipeline-yaml config option, so that it says that this option is only supported pre-mitaka

2. The customer in question was trying to use pipeline-yaml to add a different sink other than remote or event sinks, i.e. meter_sink. So I am suggesting we add a new configuration option i.e. meter-sink which would add something very similar to what remote-sink does.

Below is an excerpt from what the customer was trying to attempt with the pipeline-yaml configuration option

        sources:
          - name: 'meter source'
            meters:
             - '*'
            sinks:
             - 'meter_sink'
        sinks:
          - name: 'meter_sink'
            transformers:
            publishers:
              - http://X.X.X.X:8080/telegraf?timeout=10&max_retries=2&batch=False