Previously initConfig always returned an error even if it succeeded. This resulted in a confusing CLI error message that did not match the executed behavior. Now it returns an error only if it fails to init the config.