I am requesting to add ‘shutdown’ and ‘reboot’ privileged auto-connections to our ‘cluemaster-roomcontroller-core’ snap application that runs only on Ubuntu CORE os. This is a standalone core os device that is tightly integrated into our business software API servers and business applications. https://snapcraft.io/cluemaster-roomcontroller-core
Our software is not for general public use and is only installed on our custom PC devices sold by ClueMaster for integration into our hardware units. We require the ability to perform software rebooting and shutdown of our customer’s devices through our web interface.
Thank you for considering our request.
name: cluemaster-roomcontroller-core
description: Our software is not for general public use and is only installed on our custom PC devices sold by ClueMaster for integration into our hardware units.
snapcraft: yaml is not public and priority.
upstream: ‘PRIVATE’
upstream-relation: private
interfaces:
\shutdown:
request-type: auto-connection
reasoning: We require the ability for our customers to perform software rebooting and shutdown of our customer’s devices through our web interface.
\reboot:
request-type: auto-connection
reasoning: We require the ability for our customers to perform software rebooting and shutdown of our customer’s devices through our web interface.
the reboot interface doesn’t seem to exist however, +1 from me for auto-connect to shutdown. It is reasonable and expected functionality for the snap.
I saw that other snaps from your account have been granted shutdown in the past, however, shutdown is now a super-privileged interface. In this case, you should apply for account verification as well.
I also thought that since the software is not for general public use that a brand/dedicated store may be worth looking into to add more control for where the software can be installed.
We would love a brand store but if you are not aware, it is extremely expensive like in the $50,000 range last time I checked with Ubuntu sales team and it requires an annual support contract with an Annual Fee. It’s definitely not for small companies or startups like us. If that has changed, please let me know and I will set up a brand store right away.
Yes, you’re right about the reboot. Thank you. ‘Shutdown’ does include rebooting as well. I might need ‘hardware-observe’ as well. I can’t remember if that’s required for the shutdown interface to work properly.
Quick question about snapD. Since the snap now has auto connections for “shutdown”, will that auto update the snap already deployed on devices in the wild, or would we need to recall all the devices back to our office and uninstall/reinstall to apply the auto connection?
It should auto-connect automatically on the next refresh for that snap as far as I understand - so if you haven’t already you may need to release a new revision, which devices should refresh to automatically.
As Alex says, it’s best to release a new revision.
The automatic interfaces only apply at installation; so if you add an autoconnection like here, you can end up with people on the same revision but having installed via different assertions and thus some will have it connected and others won’t.
Releasing a new revision even if it’s just a rebuild for the sake of changing the timestamps will force everyone to download an assertion with this interface autoconnecting. The only exception would be users who’ve manually disconnected it in the past as autoconnections don’t overrule the device admin.
