Hi, thanks for your review.
Yes, that is correct, I registered the “exo” snap just to prevent eventual conflicts in the future (it seemed like an obvious thing to do).
I discussed the naming of the snap with our product people and the consensus was that the following user experience was desired if we are to use snaps:
$ sudo snap install exoscale-cli
$ exo config # Exo now performs interactive configuration, stores config in the relevant place - $HOME/snap/exoscale-cli/common/
$ exo vm list # Or any other cloud operation using exo
The above request seemed like the obvious solution.
One point of note is that the non-snap
exo program reads its configuration from “$HOME/.exoscale/” but I understand that this is not possible with snaps (I don’t think that snaps are allowed to access dotfiles in $HOME). Is that correct?
Using dotfiles in the regular place would avoid us having to add a codepath for the snap case, which would be nice.