You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the config file is written out, the default values are written out too. Thus, the fact that they represent defaults, and hence can be overridden, is lost. This means that a binary where a default is modified (say, by an upgrade), will no longer get its default although no one ever added the value to the config.
So my question is, why are default values written out? If the config is written, I end up in a situation where this doc from SetDefault is no longer true:
// Default only used when no value is provided by the user via flag, config or ENV.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
When the config file is written out, the default values are written out too. Thus, the fact that they represent defaults, and hence can be overridden, is lost. This means that a binary where a default is modified (say, by an upgrade), will no longer get its default although no one ever added the value to the config.
So my question is, why are default values written out? If the config is written, I end up in a situation where this doc from
SetDefault
is no longer true:Beta Was this translation helpful? Give feedback.
All reactions