[BUG][data-prepper] Pipeline could not be defined via pipelineConfig.config

[boris-stojnev]

Describe the bug
pipelineConfig.config could not be defined neither as a yaml object nor as a string.

To Reproduce
Steps to reproduce the behavior:

1. Install data-prepper via helm chart 0.3.1
2. Define the pipeline as part the pipelineConfig.config

pipelineConfig:
  config:
    my-pipeline:
      workers: 2
      delay: 5000
      source:
        random: {}
      buffer:
        bounded_blocking:
          buffer_size: 1024
          batch_size: 256
      processor:
        - string_converter:
            upper_case: true
      sink:
        - stdout: {}
  demoPipeline: ''
  enabled: true
  existingSecret: ''

Config will be overwritten with null value and data-prepper will not start.

If the pipeline is input as a string (as config: | ), it will be accepted by the chart and pipeline secret will be created but not well formatted and data-prepper will again not start.

Chart Name
0.3.1

Host/Environment (please complete the following information):

• Kubernetes Version: 1.33.4

Additional context
Defining pipeline via existing secret is working well. Also, defining demoPipeline: true is working as well.

[andrross]

Catch All Triage - 1 2 3