feat: Support YAML as format for the config file · influxdata/telegraf#16910

(1 留言) (1 反應) (0 負責人)Go (9,892 star) (4,161 fork)batch import

area/configurationfeature requesthelp wantedsize/l

描述

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

貢獻者指南

技術棧: go
領域: backend
議題類型: feature
難度: 4
預計時間: over 1 week
活動狀態: fresh
清晰度: clear
前置要求: Go programmingConfiguration file formats (TOML, YAML)Viper library (spf13/viper)
新手友善度: 25
研究方向: 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.