upstream-relation: I’m owner and maintainer of the project
supported-category: supported classic confinement category that the snap fits within. The list of supported categories can be found here
reasoning: Semaphore requires Ansible, Terraform, OpenTofu apps to work. Users want to use the version of the apps that they need, not the one that I can embed in the snap. I want to allow users to use the apps which installed in the system. This will greatly increase the value of the application.
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.
@alexmurray I have supported strict-mode for a long time, but now we have added support for a number of external tools. Users expect that they will work in Snap too.
The ability to remove the restriction is very important to us. Without it, we will not be able to develop our application.
Usually access to external binaries is not a reason to get classic confinement, and those packages/snaps should be staged instead.
However, in this case, as some of those applications (at least Terraform) are already using classic I think it makes sense to grant semaphore classic, as discussed for Request classic confinement for tf-wrapper
Thus I’m happy to #approve this request after publisher vetting. I’ll contact you via DM to start the publisher vetting process.
I noticed that automatic review shows an additional error due to interfaces are not allowed (or needed) with classic confinement. Your snap should passed automatic review after fixing it.
