Note the cups snap already has the following declaration within plugs:
{
"cups-control": {
"allow-auto-connection": {
"slot-snap-id": [
"m1eQacDdXCthEwWQrESei3Zao3d5gfJF"
],
"slots-per-plug": "*"
}
}
}
Which (as far as I understand it) effectively says *allow the cups-control plug of the cups snap to auto-connect to the cups-control slot on the snap with id m1eQacDdXCthEwWQrESei3Zao3d5gfJF and do greedy connection (ie connect to all cups-control slots - but since this has the slot-snap-id then this is limited to just that snap. m1eQacDdXCthEwWQrESei3Zao3d5gfJF is the snap id of the cups snap itself - this was granted previously via Request: CUPS Snap (“cups”) auto connection to of cups:cups-control to cups:admin and also of the network-manager-observe interface
So I assume that what this new request is asking is to remove this slot-snap-id and the "slots-per-plug": "*" part so that this does not auto-connect to the cups snap’s own cups-control slot and then replace it with allow-auto-connection: true. Then we likely would need to add a deny-auto-connection: slot-snap-id: m1eQacDdXCthEwWQrESei3Zao3d5gfJF to stop it auto-connecting to itself.
Or does the cups snap need to connect to both the snapd/system cups-control slot as well as it’s own?