The requested access seems appropriate, but before proceeding with the voting, @Igor do you have any insight about the official aws-cli snap? I see the last revision was uploaded 1 year and 9 months ago so it seems it is not maintained as @nysasounds is pointing out.
Can I please ask again if there has been any progress.
If there has not, can I ask again does my request really have to be blocked by getting in touch with AWS ? Can the interface be granted anyway ?
It has been a over month since my original request, I will have to do more work on this snap very likely, but everything is blocked by the request. I appreciate your help, and I would very much like to move this forward now.
Ok so looking at this request again - @nysasounds can you please name the personal-files instance to dot-aws to match the usual naming conventions?
Also perhaps it would be better to have a personal-files instance for just read permission to ~/.aws and then your snap can copy these contents (on first run) into $HOME/.aws (which will actually be ~/snap/amz-aws-cli/current/.aws which it can then modify as needed? That way you won’t need write permission to the real ~/.aws which would make me a little happier as a reviewer/. In this case, then I would be +1 for use-of a personal-files instance named dot-aws for read access to ~/.aws.
One last thing - do you wish this interface to auto-connected for your snap? If it is left as manually connected you could always use snapctl is-connected dot-aws to check and then prompt the user to manually connect it when needed?
I have renamed the personal-files interface as requested.
When I was initially thinking about how this snap would work, I was anticipating making it use the default .aws/config location in REAL_SNAP_HOME directly. But, after your suggestion I do think it may make some sense to copy any current configfound in the SNAP_REAL_HOME location to the the snap HOME.
If someone really wants to switch too the snap for their primary aws cli util, they can always create a symlink from snap home .aws to the real home .aws
i have updated the personal-files interface to read, and added a post-install hook to copy the files if there is a source and no destination yet.
Regarding interface auto-connection for personal-files, now that it’s read only. I would very much like that, yes please
Thanks @nysasounds - +1 from me for use-of and auto-connect of personal-files instance named dot-aws with read permission to ~/.aws for amz-aws-cli. Can other @reviewers please vote too?
+1 from me too for auto-connect of personal-files for read access to ~/.aws - this path stores AWS access/secret-access API keys which are required for generating API requests to access remote AWS resources, which is the primary functionality of the amz-aws-cli snap.
+2 votes for, 0 votes against, granting use-of and auto-connect of personal-files instance named dot-aws with read permission to ~/.aws for amz-aws-cli. This is now live.