support for adding secrets to deployment (superfly#3)

pinscript · Sep 13, 2022 · 5d5f1c2 · 5d5f1c2
1 parent c93b4be
commit 5d5f1c2
Show file tree

Hide file tree

Showing 2 changed files with 7 additions and 1 deletion.
diff --git a/action.yml b/action.yml
@@ -25,3 +25,5 @@ inputs:
   update:
     description: Whether new commits to the PR should re-deploy the Fly app
     default: true
+  secrets:
+    description: Secrets to be set on the app. Separate multiple secrets with a space, i.e., `FIRST_SECRET=${{ secrets.FIRST_SECRET }} SECOND_SECRET=${{ secrets.SECOND_SECRET }}`
diff --git a/entrypoint.sh b/entrypoint.sh
@@ -37,7 +37,11 @@ fi
 
 # Deploy the Fly app, creating it first if needed.
 if ! flyctl status --app "$app"; then
-  flyctl launch --now --copy-config --name "$app" --image "$image" --region "$region" --org "$org"
+  flyctl launch --no-deploy --copy-config --name "$app" --image "$image" --region "$region" --org "$org"
+  if [ -n "$INPUT_SECRETS" ]; then
+    echo $INPUT_SECRETS | tr " " "\n" | flyctl secrets import --app "$app"
+  fi
+  flyctl deploy --app "$app" --region "$region" --image "$image" --region "$region" --strategy immediate
 elif [ "$INPUT_UPDATE" != "false" ]; then
   flyctl deploy --config "$config" --app "$app" --region "$region" --image "$image" --region "$region" --strategy immediate
 fi