chore: update removal and deprecations for v1.30.0

[powersj]

This updates the various locations that v2.0.0 is used as the removal date for telegraf. As we are not doing a v2.0.0 anymore, we still want to remove many long-standing items. Using the v1.30 release is a good, round number to make that happen and this gives folks more time.

The removal of netsnmp, in favor of gosmi was not updated in config/config.go, line 530. I thought we should talk about that one first.

[srebhan]

Thanks for looking through those! Do we also want to deprecate outputs.riemann_legacy?

[powersj]

Thanks for looking through those! Do we also want to deprecate outputs.riemann_legacy?

yes - thank you for catching this. PR updated

edit: also thank you for filing the issues, I've updated #13376 with riemann_legacy

[telegraf-tiger]

Download PR build artifacts for linux_amd64.tar.gz, darwin_amd64.tar.gz, and windows_amd64.zip.
Downloads for additional architectures and packages are available below.

☺️ This pull request doesn't significantly change the Telegraf binary size (less than 1%)

📦 Click here to get additional PR build artifacts

Artifact URLs

DEB	RPM	TAR GZ	ZIP
amd64.deb	aarch64.rpm	darwin_amd64.tar.gz	windows_amd64.zip
arm64.deb	armel.rpm	darwin_arm64.tar.gz	windows_arm64.zip
armel.deb	armv6hl.rpm	freebsd_amd64.tar.gz	windows_i386.zip
armhf.deb	i386.rpm	freebsd_armv7.tar.gz
i386.deb	ppc64le.rpm	freebsd_i386.tar.gz
mips.deb	riscv64.rpm	linux_amd64.tar.gz
mipsel.deb	s390x.rpm	linux_arm64.tar.gz
ppc64el.deb	x86_64.rpm	linux_armel.tar.gz
riscv64.deb		linux_armhf.tar.gz
s390x.deb		linux_i386.tar.gz
		linux_mips.tar.gz
		linux_mipsel.tar.gz
		linux_ppc64le.tar.gz
		linux_riscv64.tar.gz
		linux_s390x.tar.gz

[srebhan]

Thanks for going through the plugins!

[Hipska]

There are a lot more deprecated plugin options, and those don't have mentioned hard coded 2.0 removal, will still say they will be removed in that version. Shouldn't those get a hard-coded version of 1.30 as well?

[srebhan]

@Hipska we decided to remove the options that are ignored by now anyway. For everything else we do have no way to help the user converting the configs (read: we do not have migrations). Therefore, for now we started out with the deprecated plugins (and hope to have migrations out till then) and options that are not used anyway. Does that make sense?

[Hipska]

There are more options that are ignored but were deprecated after 1.0 release. Those don't have a fixed removal version and dus claim to be removed in 2.0 (next major). It looks like this PR only addressed options that got deprecated in 0.xx versions.

It surely makes sense, but it simply doesn't seem complete..

[srebhan]

@Hipska let's try this first before doing big changes that we then need to revert...

[Hipska]

If it is only about removing options that were ignored/unused anyway, what could be the problem with that?