influxdata/telegraf

feat: Support YAML as format for the config file

Open

#16.910 geöffnet am 30. Apr. 2025

Auf GitHub ansehen
 (1 Kommentar) (1 Reaktion) (0 zugewiesene Personen)Go (9.892 Stars) (4.161 Forks)batch import
area/configurationfeature requesthelp wantedsize/l

Beschreibung

Use Case

Hi,

we are doing a lot of our configuration using YAML (since we're using Kubernetes), and we would like it to be possible to also use YAML as a file format for the Telegraf config file.

I know there is a large amount of dependencies on TOML, so this might be difficult/a lot of work.

Possible way to implement this, might be to use Viper for the configuration loading and Cobra for the commands https://github.com/spf13/viper https://github.com/spf13/cobra

Expected behavior

Possible to use YAML for the config file.

Actual behavior

Only TOML is supported/

Additional info

No response

Contributor Guide

Tech Stack
go
Domain
backend
Issue Type
feature
SchwierigkeitGeschätzte Implementierungsschwierigkeit für neue Contributors, von 1 für sehr kleine Änderungen bis 5 für Expertenarbeit.
4
Geschätzte ZeitEin grober Zeitrahmen, um zu recherchieren, zu implementieren, zu testen und einen Pull Request vorzubereiten.
over 1 week
AktivitätsstatusWie verfügbar das Issue gerade wirkt: frisch, aktiv, stale, blockiert oder wartet auf Maintainer-Input.
fresh
KlarheitWie klar das Issue die erwartete Änderung, Akzeptanzkriterien und den nächsten Schritt erklärt.
clear
Voraussetzungen
Go programmingConfiguration file formats (TOML, YAML)Viper library (spf13/viper)
EinsteigerfreundlichkeitEin Score von 1 bis 100, der schätzt, wie zugänglich dieses Issue für First-Time Contributors ist.
25
Research-Richtung
The feature request suggests using Viper (github.com/spf13/viper) and Cobra (github.com/spf13/cobra) to support YAML config files. The current config loading is TOML only, likely in the internal/config package. Investigate the current config parsing flow (e.g., config.NewConfig or similar). Look for any prior discussions or PRs about YAML support. Assess the impact on existing TOML based configurations. Contact maintainers via the issue to clarify if a full transition to Viper is acceptable or if a lighter approach is preferred. This is a large scope feature requiring significant refactoring.