Provide Snap package

[dex4er]

We could add Ubuntu Snap packages and distribute them in https://snapcraft.io/

Our electron-builder unfortunately does not support base option so it builds by default for core18 base.

However we can build new Snap package based on existing DEB package (see https://www.electronjs.org/docs/latest/tutorial/snapcraft#using-an-existing-debian-package) then handling Snaps would be separate job in GHA.

We can build and publish separate packages for main repo and nightly.

[dex4er]

Snap must be built outside electron-builder as the used version uses deprecated base18. Also we need additional tweaking for the manifest. Our snapcraft.yaml is mostly created from the Snap package for VScode, including the electron-launch wrapper.

Because Lens uses $HOME/.kube and $HOME/.freelens we must to build it in classic mode: strict mode protects the content of the $HOME directory.

[dex4er]

It makes less sens to distribute Snap packages outside https://snapcraft.io/ (similarly to Flatpaks outside https://flathub.org/). In that case, I'm going to remove Snaps from our releases as we need only DEB package.

[dex4er]

https://github.com/freelensapp/freelens-snap is created. We need ubuntu one account to register the package and ask for extra privileges in sandbox (~/.kube and ~/.freelens directories).

[dex4er]

So we wait... https://forum.snapcraft.io/t/re-registration-of-the-name/44782

[dex4er]

Snap package is missing in action. Nobody knows how to re-register "freelens" name. Nobody can help us.

Anyway, it'll be a big problem to register "classic" Snap package and I'm afraid the "strict" confinement package would be just useless for users, without access to the applications from host (custom authentication in .kube/config).

[dex4er]

So now we have registered package named freelens-previous-name-was-revoked. I hope it is temporarily 😆

[elephantum]

Anyway, it'll be a big problem to register "classic" Snap package and I'm afraid the "strict" confinement package would be just useless for users, without access to the applications from host (custom authentication in .kube/config).

As a heavy Lens user, I never use standard .kube/config, I have several folders of configs, one config per cluster and I setup sync of these configs.

So, for me specifically it won't be an issue

[dex4er]

@elephantum It is more about using extra authentication agents than ~/.kube/config which can be used in strict mode too. We just can't include any existing Cloud SDK to the Snap package. Flatpak can call commands from the host OS via tunnel, Snap doesn't provide such option.

I asked for classic confinement: https://forum.snapcraft.io/t/request-classic-confinement-for-freelens-previous-name-was-revoked/45663

[elephantum]

@dex4er thanks for clarification! Indeed, that's much bigger issue and we really need authentication agents to work