Hi folks, I’m working on snapping the AWS SAM CLI (https://github.com/awslabs/aws-sam-cli). The SAM CLI is a tool for publishing serverless applications on AWS.
the application documentation and the repository it’s in refer to it as “the SAM CLI” but the executable you get from installing “the SAM CLI” is sam so it seemed the package ought to be named sam-cli with an alias of sam
Someone else (no idea who) has registered the sam snap but not published anything.
Yet the aws command still can’t seem to load my config. Additionally, if I do snap run --shell sam-cli I don’t see .aws anywhere in the home directory. Should I expect it to be there?
Ah right. Ok in that case the personal-files interface is still behaving unexpectedly but in a different way: from within the snap (run --shell) I can see everything in my home directory.
If you have connected the snap to the home interface this is expected as this interface allows access to non-hidden-files-directly-under-the-home-directory in the home directory(you can still list them, but any read attempt will fail).
I haven’t connect the home interface, just the personal-files but I can see and read everything in my home directory (including file in hidden folders). Strange as everything else works just fine
Good tip, thanks. Yes that seems to work correctly. With home disconnected, I can’t see anything in my real home dir. Do you know of any example snaps with personal-files working correctly that I could try?