Configuration Errors in YAML when encountering null value

[nomalord]

When configuring vector in YAML, if a null value is encountered, a non indicative error is raised.
Basic example using amqp source (generated by the generate command):

sinks:
  output:
    inputs: [test]
    connection_string: amqp://localhost:5672/%2f
    exchange: test
    routing_key: /
    type: amqp
    encoding:
      codec: json
    healthcheck:
      enabled: true
      uri: null
    buffer:
      type: memory
      max_events: 500
      when_full: block

The error returned is:

invalid type: unit value, expected any valid TOML value

[pront]

Hi @nomalord, thanks for reporting this. Although YAML supports null, TOML doesn't. I agree we need to improve the diagnostic message here.

[jszwedko]

Related:

• configuration: formally consider null values as "option not provided" #12832

[mrzor]

I'm getting this error with no null value that I can see. A path to the value would certainly help with diagnostics. For now, comment and conquer time :)

[nomalord]

I'm getting this error with no null value that I can see. A path to the value would certainly help with diagnostics. For now, comment and conquer time :)

That makes sense, null in yaml can be represented in 2 ways:

Null_value1: null
Null_value2: 

You might have a key with no value which is interpreted as null