Classic confinement for freelens

store-requests classic-confinement
1

To make the review of your request easier, please use the following template to provide all the required details and also include any other information that may be relevant.

I understand that strict confinement is generally preferred over classic.

I’ve tried the existing interfaces to make the snap to work under strict confinement.

Note that snappy-debug can be used to identify possible required interfaces. See Debugging snaps | Snapcraft documentation for more information.

2

This request has been added to the queue for review by the @reviewers team.

3

hi @dex4er

Given the discussion in the previous topic and the details provided, freelens fits under the categories: kubernetes tools requiring arbitrary authentication agents and IDEs. The requirements for classic are understood (#approve). I will begin publisher vetting.

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

4

Hi. My Github account is the same as here: dex4er (Piotr Roszatycki) · GitHub

5

@reviewers @cav Here’s the token: freelens/.github/snap-vetting.txt at snap/vetting · freelensapp/freelens · GitHub

6

I’m not sure if it should be in the upstream repo or the repo for Snap, but here is too: freelens-snap/snap-vetting.txt at snap/vetting · freelensapp/freelens-snap · GitHub

7

that works!

Publisher is vetted. The request will be granted.

8

Request has been granted. This is now live.