A GitHub Action for executing Firebase CLI commands within CI/CD workflows, supporting deployment and management of Firebase services.
firebase-action is a GitHub Action that allows developers to run Firebase CLI commands within their GitHub Actions workflows. It automates the deployment and management of Firebase services like Hosting, Cloud Functions, Firestore, and Remote Config directly from CI/CD pipelines. The action handles authentication and command execution, streamlining the process of integrating Firebase with GitHub's automation platform.
Developers and DevOps engineers who use Firebase for their applications and want to automate deployments and management tasks through GitHub Actions. It is particularly useful for teams implementing CI/CD pipelines for Firebase-hosted projects.
Developers choose firebase-action for its simplicity and flexibility in integrating Firebase with GitHub Actions, eliminating the need for custom scripts. It supports multiple authentication methods and allows execution of any Firebase CLI command, making it a versatile tool for automating Firebase operations in CI/CD workflows.
GitHub Action for interacting with Firebase
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Allows running any Firebase CLI command by passing arguments, such as 'deploy --only hosting' or 'functions:config:set', enabling versatile automation for Hosting, Functions, and more.
Supports authentication via GCP_SA_KEY, FIREBASE_TOKEN, or GOOGLE_APPLICATION_CREDENTIALS, providing flexibility for different security setups, as detailed in the environment variables section.
Offers optional PROJECT_ID and PROJECT_PATH inputs to target specific Firebase projects and custom directory structures, simplifying multi-environment deployments.
Provides versioned Docker image releases for reliable CI/CD pipelines, plus a master branch image for testing latest features, reducing breakage from updates.
The response output was removed due to bash script issues, making it impossible to use Firebase command results (e.g., deployment URLs) in subsequent workflow steps without workarounds.
FIREBASE_TOKEN authentication is marked for deprecation, forcing users to migrate to service account keys, which adds setup complexity and potential migration headaches.
Requires assigning multiple specific Google Cloud IAM roles (e.g., Cloud Functions Developer, Firebase Hosting Admin) for GCP_SA_KEY, which can be tedious and error-prone for different Firebase services.