Add NewDefaultFoo
for configurations
#9508
Labels
area:config
good first issue
Good for newcomers
release:required-for-ga
Must be resolved before GA release
So we can say that in order to guarantee "backwards compatible behavior" user should always initialize the config with default and overwrite anything as needed instead of creating a struct with "initial value" and leave others unset.
Originally posted by @bogdandrutu in #9478 (comment)
We should add this to the contributing guidelines and, once approved, create subissues to address this on configtls, configgrpc and confighttp.
NewDefault*
functions for all config structs #9654NewDefault*
functions for all config structs #9655NewDefault*
functions for all config structs #9656NewDefault*
functions for all config structsNewDefault*
functions for all config structs #9657NewDefault*
functions for all config structs #9821The text was updated successfully, but these errors were encountered: