testflinger cli promote snap stable (#426)

* Add a github workflow to promote testflinger-cli snap from beta to stable

* When originally publishing the snap, push it to both edge and beta

We later use a workflow to promote the snap to stable, but snapcraft
does not allow publishing from the edge channel at all, it must be
pushed to another channel in order to allow promotion.

.github/workflows/cli-promote-snap.yml

@@ -0,0 +1,30 @@
+name: Promote testflinger-cli snap to stable
+on:
+  workflow_dispatch:
+    inputs:
+      snap:
+        description: 'Snap name'
+        default: 'testflinger-cli'
+        required: true
+        type: string
+      from-channel:
+        description: 'Channel to promote from'
+        default: 'latest/beta'
+        required: true
+        type: string
+      to-channel:
+        description: 'Channel to promote to'
+        default: 'latest/stable'
+        required: true
+        type: string
+
+jobs:
+  promote-snap:
+    runs-on: ubuntu-latest
+    env:
+      SNAPCRAFT_STORE_CREDENTIALS: ${{ secrets.SNAP_STORE_LOGIN }}
+    steps:
+      - name: Install Snapcraft
+        run: sudo snap install snapcraft --classic
+      - name: Promote testflinger-cli beta to stable
+        run: snapcraft promote ${{ inputs.snap }} --from-channel ${{ inputs.from-channel }} --to-channel ${{ inputs.to-channel }} --yes

.github/workflows/cli-publish-snap.yml

@@ -1,4 +1,4 @@
-name: Publish Testflinger CLI snap to edge
+name: Publish Testflinger CLI snap to edge and beta
 on:
   push:
     branches: ["main"]
@@ -21,3 +21,9 @@ jobs:
       with:
         snap: ${{ steps.build.outputs.snap }}
         release: edge
+    - uses: snapcore/action-publish@v1
+      env:
+        SNAPCRAFT_STORE_CREDENTIALS: ${{ secrets.SNAP_STORE_LOGIN }}
+      with:
+        snap: ${{ steps.build.outputs.snap }}
+        release: beta