Privileged-Interface auto-connection request for cluemaster

Hello @review-team .

I am requesting to add ‘snapd-control’ privileged interface allow-installation: true+ deny-auto-connection: false auto-connection to our business ‘cluemaster-videoplayer-core’, ‘cluemaster-mediadisplay-core’, and ‘cluemaster-roomcontroller-core’ snap applications that run only on Ubuntu CORE os and are only installed by us on devices we create for customers. This is a standalone Ubuntu Core OS device that is tightly integrated into our business software API services and business applications.

https://snapcraft.io/cluemaster-videoplayer-core

https://snapcraft.io/cluemaster-mediadisplay-core

https://snapcraft.io/cluemaster-roomcontroller-core

Our software is B2B and not for general public use, and is also set to unlisted on the Snap Store. It is only installed on our custom PC devices sold by us at ClueMaster, for integration into our hardware units. We have added a new feature to our software that allows end users to force the snap application to update through our web UI console, so they don’t have to wait for random snap refreshes. One of the main reasons for this is that the snaps sometimes update automatically when the device is actively being used by customers in their business, which causes an outage. By integrating snapd control into our snap application stack, we will have the ability to change the refresh.hold while customer games are in progress, and then release it back to normal after. Customers will also be able to send a command to our software to request the snapd api interface to do a snap refresh now and be able to self-update. This is all tightly integrated and controlled within our application stack. www.cluemaster.io

Thank you for considering our request.


  • name: cluemaster-roomcontroller-core

  • description: Our software is B2B and not for general public use. It is only installed on our custom PC devices sold by ClueMaster for integration into our hardware units.

  • snapcraft: yaml is not a public repo.

  • upstream: ‘PRIVATE’

  • upstream-relation: private

  • interfaces:

    • \snapd-control:

      • request-type: auto-connection

      • reasoning: We have added a new feature to our software that allows end users to force the snap application to update through our web UI console, so they don’t have to wait for random snap refreshes. One of the main reasons for this is that the snaps sometimes update automatically when the device is actively being used by customers in their business, which causes an outage. By integrating snapd control into our snap application stack, we will have the ability to change the refresh.hold while customer games are in progress, and then release it back to normal after. Customers will also be able to send a api command to our software to request the snapd api interface to do a snap refresh now and be able to self-update.


  • name: cluemaster-videoplayer-core

  • description: Our software is B2B and not for general public use. It is only installed on our custom PC devices sold by ClueMaster for integration into our hardware units.

  • snapcraft: yaml is not a public repo.

  • upstream: ‘PRIVATE’

  • upstream-relation: private

  • interfaces:

    • \snapd-control:

      • request-type: auto-connection

      • reasoning: We have added a new feature to our software that allows end users to force the snap application to update through our web UI console, so they don’t have to wait for random snap refreshes. One of the main reasons for this is that the snaps sometimes update automatically when the device is actively being used by customers in their business, which causes an outage. By integrating snapd control into our snap application stack, we will have the ability to change the refresh.hold while customer games are in progress, and then release it back to normal after. Customers will also be able to send a api command to our software to request the snapd api interface to do a snap refresh now and be able to self-update.


  • name: cluemaster-mediadisplay-core

  • description: Our software is B2B and not for general public use. It is only installed on our custom PC devices sold by ClueMaster for integration into our hardware units.

  • snapcraft: yaml is not a public repo.

  • upstream: ‘PRIVATE’

  • upstream-relation: private

  • interfaces:

    • \snapd-control:

      • request-type: auto-connection

      • reasoning: We have added a new feature to our software that allows end users to force the snap application to update through our web UI console, so they don’t have to wait for random snap refreshes. One of the main reasons for this is that the snaps sometimes update automatically when the device is actively being used by customers in their business, which causes an outage. By integrating snapd control into our snap application stack, we will have the ability to change the refresh.hold while customer games are in progress, and then release it back to normal after. Customers will also be able to send a api command to our software to request the snapd api interface to do a snap refresh now and be able to self-update.

This request has been added to the queue for review by the @reviewers team.

Since snapd-controlpretty much means you completely own the device (and could technically escape all confinement through it) it gets usually not granted to any snaps in the global store at all (except for some Canonical owned snaps like the snap-store/app-center or landscape-client).

You would need a dedicated brand store for using this interface.

Hello @ClueMaster :slight_smile:

As @ogra already mentioned, snapd-control is not granted for auto-connection in the Global store.

So this is a -1 vote from my side for auto-connecting snapd-control to the cluemaster snap.

Keep in mind that the use case you describe might be suitable for a brand store. Brand stores give the brand owner full control over their own snaps and devices, and the brand store reviewer may apply whatever declaration criteria make sense for the brand (including snapd-control auto-connection).

If you need any further assistance, please feel free to ping us!

Hey folks!

I agree that snapd-control is not appropriate in this case as far as the snap lives in the global store.

One of the main reasons for this is that the snaps sometimes update automatically when the device is actively being used by customers in their business, which causes an outage.

This is quite interesting as per Refresh awareness - Snap documentation

An update can be postponed for up to 14 days for a running application. The update will be either applied when the application closes, during next automatic refresh occurs without the application running, or after 14 days even if the application remains active.

What is the process to create a brand store today? Keep in mind that I’m a very small business and not a large enterprise.