fix(cli): make config create use the same file as config root

[fredbi]

fix(cli): make config create use the same file as config root
(i.e. ~/.datamon2/datamon.yaml)

• renamed config create source after actual command name
• error handling
• home dir retrieval using golang os builtin

Signed-off-by: Frederic BIDON [email protected]

[ransomw1c]

while we're in initConfig, could the viper.AutomaticEnvironment call get moved next to where viper parses the config file if present and before values are read out of viper into the config = newConfig() object?

there's something lurking about initConfig that bothers me. encoding that the generated config file must be at the same location as the config file read by initConfig is probably part of it, but i don't think that's the entire story..

.. that datamonFlags.context.Descriptor.Name is set either by env variable or flag could be part of it, although i suspect it's a combination of things.

i could approve this as a piecemeal change as is, yet i'd like to see more done about the config story.

as usual, lmk if you'd prefer approval and an addendum merge request or discussion about how to evolve the extant work here.