Juju-bin content interface for charmed-openstack-upgrader

store-requests privileged-interfaces
1

To make the review of your request easier, please use the following template to provide all the required details and also include any other information that may be relevant.

  • name: charmed-openstack-upgrader
  • description: Automatic upgrade tool for Charmed Openstack
  • snapcraft: snapcraft.yaml
  • upstream: –
  • upstream-relation: –
  • interfaces:
    • <interface-name>: juju-bin(content)
      • request-type: auto-connection
      • reasoning: charmed-openstack-upgrader now use jubilant to communicate with juju.
    • <interface-name>: dot-local-share-juju(personal-files)
      • request-type: auto-connection
      • reasoning: juju binary need write permission to $HOME/.local/share/juju to work properly.

Hi @review-team , as a published for charmed-openstack-upgrader snap I would like to request above interfaces.

Please see the following PR to understand it more:

2

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

3

+1 (#voteFor) from me for auto-connecting dot-local-share-juju as this makes sense for the snap.

Just for some extra context, is jubilant the only consumer of the content slot needed from this snap? (#askForInfo)

4

Hi Evan,

Yes, jubilant is added in the latest commit change. Before we don’t have this content slot.

5

Hey @jneo8

AFAIK the juju-bin slot is provided by the juju snap, exposing whatever the juju snap has under its bin directory. If I understand it correctly, you want the charmed-openstack-upgrader snap to be able to auto-connect to this slot and consume the files exposed by juju. If that’s the case, I think it should work without any special permission as both snaps juju and charmed-openstack-upgrader are published by Canonical.

Regarding the personal-files interface, the requested directory seems to belong to juju rather than charmed-openstack-upgrader. However, considering that both are published by the same entity I’m happy to give a +1 (#voteFor)

2 Likes
6

Voting period has ended. This request is approved with 2 votes for and 0 votes against.

7

Publisher is vetted. The request will be granted.

8

Request has been granted. This is now live.

1 Like