fix: update toml tag to match sample config / readme

[helenosheaa]

resolves #9829

[telegraf-tiger]

Looks like new artifacts were built from this PR. Get them here!

Artifact URLs

• i386.rpm

• freebsd_i386.tar.gz

• linux_i386.tar.gz

• i386.deb

• s390x.rpm

• linux_s390x.tar.gz

• s390x.deb

• ppc64le.rpm

• linux_ppc64le.tar.gz

• ppc64el.deb

• x86_64.rpm

• freebsd_amd64.tar.gz

• linux_amd64.tar.gz

• amd64.deb

• aarch64.rpm

• linux_arm64.tar.gz

• arm64.deb

• linux_mips.tar.gz

• mips.deb

• linux_mipsel.tar.gz

• mipsel.deb

• armv6hl.rpm

• freebsd_armv7.tar.gz

• linux_armhf.tar.gz

• armhf.deb

• armel.rpm

• linux_armel.tar.gz

• armel.deb

• static_linux_amd64.tar.gz

• windows_amd64.zip

• windows_i386.zip

• darwin_amd64.tar.gz

[srebhan]

Looks good to me.

[powersj]

My only concern is if folks are using "headers" already, they will have breakage in the next version. Instead, should the documentation get updated to show "headers" as the correct value?

[helenosheaa]

@powersj yeah I was sort of torn between which is less disruptive. The http_headers key is what was in the readme and in the sample config so anyone who figured out they needed to use headers instead would have had to go looking in the plugin code for it.

Considering the plugin has only been around since 1.18 I thought making it match the spec would be ok. However happy to change the readme instead, thoughts?

[powersj]

It sounds like merging this as-is makes sense, as we have not received an issue about this till now.