influxdata/telegraf

feat: Support YAML as format for the config file

Open

#16 910 ouverte le 30 avr. 2025

Voir sur GitHub
 (1 commentaire) (1 réaction) (0 assignés)Go (9 892 stars) (4 161 forks)batch import
area/configurationfeature requesthelp wantedsize/l

Description

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

Guide contributeur

Stack technique
go
Domaine
backend
Type d'issue
feature
DifficultéDifficulté estimée pour un nouveau contributeur, de 1 pour un très petit changement à 5 pour un travail expert.
4
Temps estiméFourchette de temps approximative pour investiguer, implémenter, tester et préparer une pull request.
over 1 week
Statut d'activitéDisponibilité apparente de l'issue : fraîche, active, ancienne, bloquée ou en attente d'un mainteneur.
fresh
ClartéClarté avec laquelle l'issue explique le changement attendu, les critères d'acceptation et la prochaine étape.
clear
Prérequis
Go programmingConfiguration file formats (TOML, YAML)Viper library (spf13/viper)
Accessibilité débutantScore de 1 à 100 estimant l'accessibilité de cette issue pour un premier contributeur.
25
Direction de recherche
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.