build fluxctl snap using GH action

.github/workflows/docs.yaml

@@ -43,6 +43,6 @@ jobs:
         id: lc
         uses: peter-evans/link-checker@v1
         with:
-          args: -d ./site -r ./site
+          args: -d ./site -r ./site -x man7.org
       - name: Fail if there were link errors
         run: exit ${{ steps.lc.outputs.exit_code }}

.github/workflows/fluxctl-snap.yaml

@@ -0,0 +1,31 @@
+name: Build snap
+
+on:
+  push:
+    branches:
+      - master
+
+jobs:
+  build-snap:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Check out Git repository
+        uses: actions/checkout@v2
+
+      - name: Install Snapcraft
+        uses: samuelmeuli/action-snapcraft@v1
+        with:
+          snapcraft_token: ${{ secrets.snapcraft_token }}
+          use_lxd: true
+
+      - name: Run Snapcraft build
+        run: sudo snapcraft --use-lxd
+
+      - name: Upload to Snapcraft store (edge channel for revs in master)
+        if: ${{ ! startsWith(github.event.ref, 'refs/tags') }}
+        run: snapcraft push --release edge fluxctl_*.snap
+
+      - name: Upload to Snapcraft store (stable channel for tagged releases)
+        if: ${{ startsWith(github.event.ref, 'refs/tags') }}
+        run: snapcraft push --release stable fluxctl_*.snap

docs/faq.md

@@ -241,7 +241,7 @@ If you have installed flux through Helm, make sure to pass
 
 As part of using git+ssh securely from the Flux daemon, we make sure
 `StrictHostKeyChecking` is on in the
-[SSH config](http://man7.org/linux/man-pages/man5/ssh_config.5.html). This
+[SSH config](https://man7.org/linux/man-pages/man5/ssh_config.5.html). This
 mitigates against man-in-the-middle attacks.
 
 We bake host keys for `github.com`, `gitlab.com`, `bitbucket.org`, `dev.azure.com`, and `vs-ssh.visualstudio.com`