What are you trying to do?

I'm trying to execute multipass info from within another (strictly confined) snap.

What's your proposed solution?

According to @ogra:

"the only proper solution here would be if multipass exported all its binaries through a content interface that another snap could then consume"

As far as I understand, multipass snap should add something like this:

slots:
  multipass_binary:
    interface: content
    content: multipass_binary
    source:
      read: 
        - $SNAP/bin/multipass

Additional context

I have initiated a small project named multipass-exporter to expose Multipass' metrics in Prometheus format.

To create multipass metrics, the tool executes multipass info, but if the tool is packed in a strictly confined snap then it has no access to multipass binary.