Config file written insecurely

[heph]

The livetail-cli config file is written as $(pwd)/config.json in plain-text with world-readable permissions (644). This has several problems.

1. Using the current directory instead of expanding $HOME or ~ means the same config file cannot be reused when the user changes their directory, and is likely to result in multiple copies of sensitive credentials strewn all over the user's filesystem.
2. The file should be explicitly set mode 0600 when written.
3. The config file should be a "dot" file (.config.json)
4. The config file should be called something more explicit to avoid clobbering non-livetail-cli config files (e.g. ~/.sumo-livetail)

Also you should support #9 so the user doesn't need to risk storing sensitive credentials on their filesystem in the first place if they have a better option.

[miahorg]

I would add that profiles should be supported should you find yourself in the situation where you have multiple accounts query. This could be done with the command line flag "--profile ".

This is done with the AWS CLI apps quite nicely. Credentials are stored in ~/.aws/credentials and the configuration is stored in ~/.aws/config. Within these files a default can be set as well as setting specific to each profile.