Canonical Livepatch: Request for manual connection of a new machine-token slot

name: canonical-livepatch
description: Official client for the Canonical Livepatch service.
snapcraft: PRIVATE
upstream: PRIVATE
upstream-relation: maintainer
slots:
  machine-token:
    interface: content
    attributes:
      content: canonical-livepatch-machine-token
      source:
        read:
          - $SNAP_COMMON/livepatch-token
    request-type: manual-connection
    reasoning: Enables the livepatch admin snap to connect and securely read the machine token. The admin snap requires this token to query the hosted server and download patches in bulk for offline on-prem sync.
1 Like

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

Hello @kunalmohan-cncl :slight_smile:

The use case is legitimate and consistent with the snap’s purpose, so this is a +1 from me, for use of the machine-token content slot with manual-connection!

As per content interface - Snap documentation, any snap can manually connect to a content slot if the “content” attribute matches. Given that both snaps, canonical-livepatch-server-admin and canonical-livepatch are published by the same entity, you will even get auto-connection by default in this case.

Could you please further explain what issues are you finding to get this connection working?

Thanks!

1 Like