I’m asking for classic confinement approval for the model-builder snap.
This GUI snap orchestrates snapd and snapcraft to create Ubuntu Core model assertions with the ability to use it across different snap stores (brand/global). It is supposed to eventually move under the Canonical or Ubuntu store accounts to be available to Canonical customers as well as the wider Ubuntu Core community to ease the creation of Ubuntu Core images.
For the time being I would like to keep it under my personal account though and have started the vetting process at Star developer request for Oliver Grawert
- name: model-builder
- description: GUI for creating and signing Ubuntu Core model assertions
- snapcraft: ubuntu-core-model-builder/snap/snapcraft.yaml at main · ogra1/ubuntu-core-model-builder · GitHub
- upstream: https://github.com/ogra1/ubuntu-core-model-builder
- upstream-relation: Owner/Creator
- supported-category: tools for local, non-root user driven configuration of/switching to development workspaces/environments
- reasoning: The snap uses snapcraft and snapd features that are not accessible through any of the existing APIs (or the snapd socket (for i.e. signing of model assertions)). Along with this it requires use of the existing snapcraft login and key management.
[x ] I understand that strict confinement is generally preferred over classic.
[x ] 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 https://snapcraft.io/docs/debug-snaps for more information.