Aliases didn't enable out of the box

[Alan Pope 🍺🐧🐱 🦄]

I have an application which contains numerous binaries, so I thought I'd use aliases as per the guide at:-

https://insights.ubuntu.com/2017/01/28/ubuntu-core-how-to-enable-aliases-for-your-snaps-commands/

However, after installing my snap, the aliases are in this state:-

App Alias Notes
mitmproxy.mitmdump mitmdump -
mitmproxy.mitmweb mitmweb -
mitmproxy.pathoc pathoc -
mitmproxy.pathod pathod -

I had to "snap alias mitmproxy mitmweb" each one to get to:-

App Alias Notes
mitmproxy.mitmdump mitmdump enabled
mitmproxy.mitmweb mitmweb enabled
mitmproxy.pathoc pathoc enabled
mitmproxy.pathod pathod enabled

I would have expected these to auto-enable or tell me what to do when I installed the snap. It did neither, so as a user, I wasn't aware any post-install alias enabling needed to be done.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Samuele Pedroni (pedronis)]

We are likely moving away from having aliases defined explicitly in the snap, snap.yaml at all.

Nevertheless what is true and will stay true is that because aliases all share a global name space and may cause conflicts, they need some custodianship over that name space,

at the moment aliases can be auto-enabled similarly as auto connection for privileged interfaces (via assertions), these need to be discussed on the user mailing list or discussed with a reviewer during a review process (though not atm nor when they will not be in snap.yaml anymore obviously they trigger a manual review).

[Samuele Pedroni (pedronis)]

aliases are not defined in the snaps themselves at all anymore since 2.26,

there are only manual aliases

and store auto-enabled ones