Hi,
I’d like to request that testflinger-cli have read access to ~/.config/testflinger-cli.conf and write access ~/.local/share/testflinger-cli-history.json as defined by the plugs in the PR attached below.
Testflinger is “a system for orchestrating the time-sharing of access to a pool of target machines.” It’s used within Canonical to provision and test lab machines.
Let me know if you need anything!
+1 from me - testflinger-cli is the clear owner of these paths - but one quick thing - your PR upstream should be updated since you have the dot-local-share-testflinger-cli-history plug in the slots section - but it should be in plugs for the testflinger-cli app.
I guess I have a question, would you recommend we use the personal-files or ensuring the snap uses the snap data directories? We could do either, and we’re not 100% sure which one to go with yet.
If an application already exists outside of the snap ecosystem and hence would be using existing paths like ~/.config to store its data, then it makes sense to use personal-files for the snap so it can reuse this existing config if it already exists. And any existing documentation for the application which refers to such paths for config files etc doesn’t need to be updated for the snap specific case.
However, my understanding is that testflinger-cli is only distributed as a snap, in which case it should just use SNAP_USER_DATA or SNAP_USER_COMMON to store its configuration etc. ie. in general a snap should prefer to use the snap data directories unless it has a good reason not to.
@alexmurray Okay, I think we will change the environment variables to ensure that the snap uses SNAP_USER_DATA, SNAP_USER_COMMON, etc. Thank you for the clarification! 
