This is a fork of https://github.com/w9jds/firebase-action that uses node 14 instead of 16
This Action for firebase-tools enables arbitrary actions with the firebase
command-line client.
args
- Required. This is the arguments you want to use for thefirebase
cli
response
- The full response from the firebase command current run (Will most likely require a grep to get what you want, like URLS)
-
FIREBASE_TOKEN
- Required if GCP_SA_KEY is not set. The token to use for authentication. This token can be aquired through thefirebase login:ci
command. -
GCP_SA_KEY
- Required if FIREBASE_TOKEN is not set. A normal service account key(json format) or a base64 encoded service account key with the needed permissions for what you are trying to deploy/update. If you're deploying functions, you would also need theCloud Functions Developer
role, and theCloud Scheduler Admin
for scheduled functions. Since the deploy service account is using the App Engine default service account in the deploy process, it also needs theService Account User
role. If you're only doing Hosting,Firebase Hosting Admin
is enough. https://firebase.google.com/docs/hosting/github-integration -
PROJECT_ID
- Optional. To specify a specific project to use for all commands. Not required if you specify a project in your.firebaserc
file. If you use this, you need to giveFirebase Viewer
permission roles to your service account otherwise the action will fail with authentication errors. -
PROJECT_PATH
- Optional. The path to the folder containingfirebase.json
if it doesn't exist at the root of your repository. e.g../my-app
-
CONFIG_VALUES
- Optional. The configuration values for Firebase function that would normally be set withfirebase functions:config:set [value]
To authenticate with Firebase, and deploy to Firebase Hosting:
name: Build and Deploy
on:
push:
branches:
- master
jobs:
build:
name: Build
runs-on: ubuntu-latest
steps:
- name: Checkout Repo
uses: actions/checkout@master
- name: Install Dependencies
run: npm install
- name: Build
run: npm run build-prod
- name: Archive Production Artifact
uses: actions/upload-artifact@master
with:
name: dist
path: dist
deploy:
name: Deploy
needs: build
runs-on: ubuntu-latest
steps:
- name: Checkout Repo
uses: actions/checkout@master
- name: Download Artifact
uses: actions/download-artifact@master
with:
name: dist
path: dist
- name: Deploy to Firebase
uses: flowclub/firebase-action@master
with:
args: deploy --only hosting
env:
FIREBASE_TOKEN: ${{ secrets.FIREBASE_TOKEN }}
Alternatively:
env:
GCP_SA_KEY: ${{ secrets.GCP_SA_KEY }}
If you have multiple hosting environments you can specify which one in the args line.
e.g. args: deploy --only hosting:[environment name]
If you want to add a message to a deployment (e.g. the Git commit message) you need to take extra care and escape the quotes or the YAML breaks.
with:
args: deploy --message \"${{ github.event.head_commit.message }}\"
Starting with version v2.1.2 each version release will point to a versioned docker image allowing for hardening our pipeline (so things don't break when I do something dump). On top of this, you can also point to a master
version if you would like to test out what might not be deployed into a release yet by using something like this:
name: Deploy to Firebase
uses: docker://flowclub/firebase-action:master
with:
args: deploy --only hosting
env:
FIREBASE_TOKEN: ${{ secrets.FIREBASE_TOKEN }}
The Dockerfile and associated scripts and documentation in this project are released under the MIT License.
If you decide to do seperate jobs for build and deployment (which is probably advisable), then make sure to clone your repo as the Firebase-cli requires the firebase repo to deploy (specifically the firebase.json
)