build fluxctl snap using GH action

[dholbach]

Retrying #3034 after reading samuelmeuli/action-snapcraft#11 (comment)

Build snap using GH action... next steps:

• confirm build works
• add secrets to access snap store
• commits to master: publish in edge channel
• releases: publish in stable channel

[dholbach]

https://github.com/dholbach/flux/runs/699917271 looks good! :-)

[dholbach]

✔️ https://github.com/dholbach/flux/runs/708796834 (with snapcraft_token added to my repo too).

[dholbach]

To add some background: for every commit to master, this GH Action workflow

• builds the snap using snap/snapcraft.yaml
• if it's a tagged release, upload the resulting snap to the stable channel of the snap
• if not, upload the resulting snap to the edge channel

Up until now I did this all manually (for releases and for commits in master every other day), because we were blocked by canonical-web-and-design/build.snapcraft.io#1191 (to set up the webhook automatically, build.snapcraft.io wanted very broad privileges).

This would automate it all away.

[squaremo]

On the basis that I this demonstrably works, and I can see how to debug it when it doesn't, I approve this PR. Thanks Daniel! 🍍

[dholbach]

	ERROR	https://man7.org/linux/man-pages/man5/ssh_config.5.html
		X509: certificate signed by unknown authority

Firefox says it's "Let's Encrypt". 🤷

[dholbach]

I guess I can just exclude man7.org from being checked?

[hiddeco]

@dholbach it might also be solved by updating the ca-certificates package in the docs.yaml GitHub Action.

[dholbach]

💡

[dholbach]

Apparently it was already installed, so I'll remove it again and exclude man7.org.