vt: set toml file mod

[micsthepick]

Set 0600 as the mode for the config file.

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[micsthepick]

@plusvic I can certainly agree to a cla, but this repo has neither a security.md nor a contributing.md?

[plusvic]

I don't think this should be done here. I would put this in the init command, where the .vt.toml file is initially created.

vt-cli/cmd/init.go

Line 92 in eb5dbbc

configFile, err := os.Create(configFilePath)

[micsthepick]

would we still know where the config path is from though? the current solution grabs the correct path from the lib (maybe this is an upstream issue anyways?)

[micsthepick]

I say that because it seems as if the path may be configured through command line args?

[plusvic]

The path for the config file is always the user's home directory. My concern with the proposed change is that the file permissions are set on every execution of the tool, and the file is created if it doesn't exist. This shouldn't be tool's behavior in my opinion. The config file should be created only when the init command is executed, and I agree on setting 0600 permissions when the file is initially created, as it contains the user's API key and it shouldn't be visible to other others.

However, if the user later decides to change the initial permissions for whatever reason, the tool shouldn't be enforcing 0600 permission every time it runs.