search

Joel-Valentine / cogo

CLI tool to interact with different cloud providers
https://cogoapp.dev
MIT License
2 stars 0 forks source link

Config file location #1

Closed Joel-Valentine closed 4 years ago

Joel-Valentine commented 4 years ago

Currently the config file will be picked up when calling cogo from the same directory as .cogo_config.json. This obviously isn't great for an app thats supposed to be independent of working directories.

Currently the config uses viper to manage reading this config file AND writing the config file when it detects there isn't already one present (User is asked if they would like to create it).

I know there are many different types of configs/secret management that can be used within viper. Perhaps using env variables isn't too bad? Or maybe there needs to be a generalised location for the config file such as ~/.config/cogo similar to how https://wtfutil.com/configuration/ is done

Joel-Valentine commented 4 years ago

285229c153e76ed9bcd4ddecb9a7a19754f8841a closes this