Missing stim config causes error

[dwilson6]

If I already have a vault token and use stim (running the stim docker container) to get kube config, it errors and complains that the ~/.stim/config.yaml file doesn't exist. It would be nice if stim would check if it needs the config file to run the command or at least have the docker container create an empty config file

[lwahlmeier]

do you mean the warning:

2019-06-25 19:54:06.8682203	[ WARN  ]	No config file exits at :"/home/<user>/.stim/config.yaml"

?
If so I dont think its appropriate to completely removing this, even with a valid token and vault addr set. There are plenty of other things that could be needed from the config if its missing. Could probably improve the IsAutomated() check and maybe even add a cli/env flag for it so it skips certain user errors/warns in that case. Does that sound like an appropriate solution?

[dwilson6]

The warning is fine. It actually errors. In this case, it is writing to the file so maybe it could create it if it doesn't exist. Or maybe a cli flag to force IsAutomated() to be true.

Below is the output from running VAULT_TOKEN='...' stim kube config ... without a config file.

2019-06-26 11:40:25.566293	[ WARN  ]	No config file exits at :"/home/<user>/.stim/config.yaml"
2019-06-26 11:40:25.566446	[ WARN  ]	Issue loading config file use -verbose for more info
2019-06-26 11:40:25.568909	[ WARN  ]	Stim-vault: time: invalid duration
2019-06-26 11:40:25.870283	[ FATAL ]	Stim-Vault: Error Updating username in configuration file: open /home/<user>/.stim/config.yaml: no such file or directory

[lwahlmeier]

Ahh yeah thats a problem.