Classic confinement for Snap `jsonschema`

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.

Also, I’m not sure if its because of the lack of classic confinement permission, but while I do see the jsonschema Snap name as registered on my Snapcraft dashboard, I still get an error publishing it, which led me to this forum:

resource-not-found: Snap not found for name=jsonschema

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

Hi @review-team, is there any update regarding this? We would love to have the CLI up on the Snap store!

Hi @jviotti!

I’m not sure this snap is a suitable candidate for classic confinement (#reject), as it doesn’t appear to fall under the debug-tools category. Regarding your concerns about access to the environments directory, users can typically use the $HOME directory for their environments instead.

In general, we avoid granting classic confinement solely for the purpose of accessing arbitrary files on the system due to user inertia.

As for the resource-not-found: Snap not found for name=jsonschema error, this occurs because the snap has not been published. It failed the automated review due to the request for classic confinement.

Please let me know if you have any further questions or if there’s anything else I can help with!

Alright. Let’s try to have it restricted to HOME to begin with and see how it goes!