Thank you for your suggestions!
I do not think that shipping the needed tools in the snap would solve the problem. A real-world usecase in a CI/CD pipeline might look like this:
- run some general system updates
- check that there is enough disk space available
- install the new version of the software
- run some checks to verify that the installation process was successful
Thus it would not be possible to foresee all the commands which might be needed for the end user. I am afraid that if only a restricted subset of commands are available, the application is not usable in practical scenarios any more.
Would there be an option to publish with
classic confinement to only
I have also considered just publishing the snap with GitHub releases and asking the users to install it manually, but this way there is no good way to handle updates.