[v2] Add support for optional fields for config struct #5828
Labels
area/otel
good first issue
Good for beginners
help wanted
Features that maintainers are willing to accept but do not have cycles to implement
v2
Looking for a volunteer to add support for optional fields for config structs.
Objective: create a draft PR with a prototype solution outlined in go-viper/mapstructure#37 (make sure it's a
draft
to avoid creating notifications noise to go-viper maintainers). Update this ticket with a link so that we can collaborate on that prototype.The text was updated successfully, but these errors were encountered: