Personal file access request for bunyan-logviewer

store-requests
1

The logviewer cli application needs to read its configuration from ~/.config/logviewer/config.yaml or ~/.logviewer as a backup (if XDG folders are not used).

2

@gildas - just to clarify, is manual or auto connection being requested?

3

@gildas - ping, can you please provide the requested information?

4

@cav, sorry I missed the question earlier. It would need auto-connect based on another tool of mine that needed the same type of access (Personal file access request for bitbucket-cli - #4 by gildas)

5

Hi @gildas - no dramas!

This sounds reasonable to me given the config file is owned by bunyan-logviewer. So +1 from me!

6

Hello @gildas! While reviewing the snap’s YAML file, I noticed that it uses the write field instead of read. Could you confirm whether you actually need write, read, or both permissions for these paths?

Also, a small note. Since the snap is called bunyan-logviewer, would you consider using the paths $HOME/.config/bunyan-logviewer/config.yaml and $HOME/.bunyan-logviewer instead?

Thanks!

7

Hello @yomonokio,

You’re right, that’s an oversight and bad copy/paste from ny bitbucket-cli (where that tool can change its config files). I will change it to read.

Changing the path name is a bit more difficult as the tool is already in use by quite a few people and I would hate forcing them to change, just because I created a snap.

I called the snap this way to avoid clashing with potentially other tools that could be called logviewer.

8

@yomonokio, now what if I call the snap logviewer?

9

In the meantime, uploaded a new revision #2

10

Unfortunately, the name logviewer is already taken. So, in case changing the path names is not an option, I can also support the current request with a +1, but this would require publisher vetting as per Process for performing Snap Publisher Vetting.

11

Fair enough, thanks for checking.

Out of curiosity, does the fact I was vetted for bitbucket-cli help the publisher vetting here?

12

Found the publisher vetting chat from Jan 2024, in case it helps.

13

hi @gildas - sorry for the delay!

+2 votes for, 0 votes against, granting auto-connect of interface personal-files to bunyan-logviewer. I will begin publisher vetting for this snap.

Could you please provide your github account associated with the upstream project.

14

Thanks! Here you go: github.com/gildas

15

publisher is now vetted. This is now live.

Thanks!

1 Like