Request for confinement 'classic' for 'auto-sys-config'

[emitorino]

Hey @raman005 ,

If you see the process-for-reviewing-classic-confinement-snaps:

• difficulty making strict confinement work

Fits into the unsupported category. This combined with the explanation from @ogra

@ogra

Snaps have to be self contained, no matter which confinement model they use, they have to ship all their runtime dependencies so that your snap can run seamlessly on gentoo, arch, fedora, yocto, nixOS etc… this completely rules out any calls to external native package managers like rpm or apt

means that unfortunately auto-sys-config do not fit the criteria to be granted classic.

Based on the explanation provided by @dio, this seems to be a snap to be installed in the lab. So just to be clear:

@dio

If to fit “3rd party installer snaps” means that we have to manage and distribute our snap through the Snap Store. We can totally do so.

On the other hand, your team does not need to distribute it through the Snap Store unless its a requirement for the lab setup/configuration. Your team can always built and install it locally. If publishing it to the store is a requirement, we can explore other options, like the use of interfaces like: packagekit-control, ssh-keys, system-files and others to make auto-sys-config work under strict confinement.