1218 results found

1. API to add authorized domains to the authentication module
   3 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Authentication  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. views on data

   Firestore should support a simple language like the rule language that allows modifying the data before sending it to clients.

   The primary use case is changing or hiding some fields depending on the auth uid

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Firestore  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Evaluate Mutation Results in Realtime Refresh Conditions & Support Mutation-Side Triggers

   Currently, when configuring a refresh condition on a query, the condition can only evaluate the triggering mutation's variables and auth (uid/token). We cannot check the actual result (response) of the mutation.

   This creates a significant friction point when mutations are executed from non-client environments, such as a Cloud Function triggered by another backend service (e.g., Firebase Storage). Because the Cloud Function executes without the end-user's auth context, the only way to accurately filter the query refresh is to pass the userId into the mutation's variables. This feels like an unnecessary workaround just to satisfy the refresh condition.

   To make real-time cache invalidation cleaner and more robust for server-side triggers, you need

   • Access to Mutation Results in Query Conditions
   • Mutation-Driven Triggers:

   Currently, when configuring a refresh condition on a query, the condition can only evaluate the triggering mutation's variables and auth (uid/token). We cannot check the actual result (response) of the mutation.

   This creates a significant friction point when mutations are executed from non-client environments, such as a Cloud Function triggered by another backend service (e.g., Firebase Storage). Because the Cloud Function executes without the end-user's auth context, the only way to accurately filter the query refresh is to pass the userId into the mutation's variables. This feels like an unnecessary workaround just to satisfy the refresh condition.

   To make real-time… more

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  SQL Connect (Data Connect)  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Production Multi-Provider Integration Scheme For production readiness, for the Google IO 2027 release

   Production Multi-Provider Integration Scheme For production readiness, for the Google IO 2027 release a service that after staring into your devices camera for 20 seconds will log you into any account email platform or social media that's ever log your face and stored it in the cloud

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Authentication  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. Add support for pnpm workspaces

   While it does support for pnpm, it does not support pnpm workspaces. The reason for this is because it currently looks for the pnpm-lock.yaml file in the workspace app directory, but this file is actually in the root directory when using workspaces. This causes lots it to switch to using npm and the build to fail.

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  App Hosting  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. Integrate Firebase product and developer notifications with Google Cloud Essential Contacts

   Larger customers often use Google Cloud Essential Contacts for ensuring critical notifications get to the right people. Currently Firebase product and developer communications seem to go out via email to named user accounts where the customer has no control who this goes to and it may miss its intended audience.

   It would be great if FIrebase notifications could be integrated with Google Cloud Essential Contacts to give customers more control over where critical notifications go to and to make this consistent with other Google Cloud services.

   https://docs.cloud.google.com/resource-manager/docs/managing-notification-contacts

   Thank you!

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Other  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Request to make "flutter deploy" to allow Incremental Remote Config parameters update

   Take this case,

   An Enterprise Project with multiple Mobile Apps underneath. In our case, it is an ERP system with multiple subject-based mobile apps. Each mobile app needs to control its forced-update on the client side. Remote Config is thought to be the way forward.

   We need to have "flutter deploy" update a parameter for each app, to keep the latest version. The app will check this against its bulit-in version number. If a mismatch, then force an update. Very typical scenario.

   The issue with the current "flutter deploy" as a method to automatically update/maintain Remote Config parameter for the App, is that is erases all other parameters for all other apps in the same project !!

   A remote config file such as
   {
   "parameters": {
   "myapplatestversion": {
   "defaultValue": {
   "value": "A2001-AI0109"
   },
   "valueType": "STRING"
   }
   }
   }

   is missing a directive, to state if this is a New (Add) or Update, or Overwrite the entire project partameters.

   Currently, the firebase Console allows this sort of incremental maintenance of the project parameters. Therefore, it is only normal to expect the Deploy API to provide the same functionality of the portal.

   We are willing to help, if you need an extra hand to program the feature !

   Take this case,

   An Enterprise Project with multiple Mobile Apps underneath. In our case, it is an ERP system with multiple subject-based mobile apps. Each mobile app needs to control its forced-update on the client side. Remote Config is thought to be the way forward.

   We need to have "flutter deploy" update a parameter for each app, to keep the latest version. The app will check this against its bulit-in version number. If a mismatch, then force an update. Very typical scenario.

   The issue with the current "flutter deploy" as a method to automatically update/maintain Remote Config parameter for the… more

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Remote Config  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. Perform automatic rollouts only for changes to configured app directory

   I have a Next.js app within a monorepo for my Firebase project, which also includes an iOS and Android app, each in their own directories. My App Hosting backend is configured for the Next.js app directory, but it appears that the automatic rollouts feature does not take this setting into account when changes are pushed to the repo. I don't want to perform a rollout when making changes only the iOS app, for example.

   Automatic rollouts should only perform the rollout (or be able to be configured to) only when the specified app directory contains changes. Path matching is a common feature in CI/CD and I'm surprised to find that this isn't the default behavior. We should be able to specify which path(s) App Hosting monitors for changes, so that it doesn't needlessly roll out every time I make a change in the monorepo that doesn't affect the app.

   I have a Next.js app within a monorepo for my Firebase project, which also includes an iOS and Android app, each in their own directories. My App Hosting backend is configured for the Next.js app directory, but it appears that the automatic rollouts feature does not take this setting into account when changes are pushed to the repo. I don't want to perform a rollout when making changes only the iOS app, for example.

   Automatic rollouts should only perform the rollout (or be able to be configured to) only when the specified app directory contains changes. Path matching is a… more

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  App Hosting  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. Persistent Memory & "Do Not Modify" Toggles to Protect Existing Code

   As a project becomes more developed, I've noticed that the Gemini assistant in Firebase Studio sometimes starts modifying templates, forms, and functions that were already working perfectly.

   To prevent this, I currently have to prepend a strict warning to every single prompt: "Proceed with extreme caution. Do not change the visual design, menus, structure, or any logic unrelated to this specific query: [my actual prompt]". While this workaround is effective and usually results in better code, it is tedious to write every time.

   My Suggestion: It would be incredibly helpful to implement a "Context Memory" feature with a checklist or on/off toggles. This would allow developers to explicitly mark certain functions, files, or UI layouts as "Locked/Remember" (Gemini must preserve them) and others as "Modifiable". This way, we wouldn't have to constantly use defensive prompting to protect the code that is already finished and working.

   As a project becomes more developed, I've noticed that the Gemini assistant in Firebase Studio sometimes starts modifying templates, forms, and functions that were already working perfectly.

   To prevent this, I currently have to prepend a strict warning to every single prompt: "Proceed with extreme caution. Do not change the visual design, menus, structure, or any logic unrelated to this specific query: [my actual prompt]". While this workaround is effective and usually results in better code, it is tedious to write every time.

   My Suggestion: It would be incredibly helpful to implement a "Context Memory" feature with a checklist or… more

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Agent Skills  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. Add copy source code to Firestore Query Builder

    It'd be great if Query Builder had a way to translate whatever query you're running into a code snippet. Something like Firestore's docs where you can select a language and then copy the code.

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Firestore  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. Add command to check Firebase CLI authentication status without triggering reauth

    Currently, the Firebase CLI does not provide a way to proactively check whether the user’s authentication state is still valid. Authentication validity is only discovered when running a command that requires auth, at which point the CLI may fail and instruct the user to run firebase login --reauth.

    This makes it difficult to:
    • Detect impending or current auth expiration ahead of time
    • Build scripts or tooling that can validate environment readiness
    • Provide a better UX in local development workflows
    • Perform lightweight “health checks” without risking mid-command failure

    Problem
    There is no supported command such as:
    • firebase login:status
    • firebase auth:check
    • or similar

    The only way to determine auth validity today is to run a real command (e.g. firebase projects:list) and handle a failure, which is reactive and indirect.

    Proposed Solution
    Introduce a command that checks CLI authentication status without performing a project operation, for example:

    firebase login:status

    Possible behaviors:
    • Exit code 0 if credentials are present and refreshable
    • Exit code 1 if credentials are missing, expired, or require reauthentication
    • Optional human-readable output, e.g.:
    • “Authenticated (user@example.com)”
    • “Authentication expired — run firebase login --reauth”

    Optional enhancements:
    • --json output for scripting
    • Indicate auth method (user OAuth vs service account)
    • Indicate whether silent refresh succeeded

    Why this would be useful
    • Improves developer experience
    • Enables deterministic preflight checks in scripts
    • Reduces surprise failures during deploys
    • Aligns with similar tooling (gcloud auth list, aws sts get-caller-identity, etc.)

    Scope clarification
    This request is specifically about Firebase CLI authentication, not Firebase Auth sessions or Admin SDK behavior.

    Alternative workaround (current)
    Running a harmless command like firebase projects:list is currently the only way to infer auth state, but this is indirect and not ideal.

    Currently, the Firebase CLI does not provide a way to proactively check whether the user’s authentication state is still valid. Authentication validity is only discovered when running a command that requires auth, at which point the CLI may fail and instruct the user to run firebase login --reauth.

    This makes it difficult to:
    • Detect impending or current auth expiration ahead of time
    • Build scripts or tooling that can validate environment readiness
    • Provide a better UX in local development workflows
    • Perform lightweight “health checks” without risking mid-command failure

    Problem
    There is no supported command such as:
    •… more

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Firebase CLI  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. Update privacy policy part of PNV SDK

    About the new post on the Google Groups of PNV SDK:
    https://groups.google.com/g/firebase-pnv-announce/c/44tx7z_Pc8w/m/99O0BfW4AAAJ?utm_medium=email&utm_source=footer
    https://firebase.google.com/docs/phone-number-verification/android/get-started

    "You must have a publicly accessible privacy policy to complete OAuth brand verification. You can use Firebase Hosting to create a basic web app to host your test privacy policy."

    It mentions to have privacy policy related to this, but doesn't mention what to put there.
    I tried to contact Firebase support, and they said to me to request it here, with these details:

    "
    It should clearly say, in simple words:
    that your app reads the user’s phone number,
    why it does this,
    whether the number leaves the device or is sent to any server,
    and how users can contact you.
    "

    About the new post on the Google Groups of PNV SDK:
    https://groups.google.com/g/firebase-pnv-announce/c/44tx7z_Pc8w/m/99O0BfW4AAAJ?utm_medium=email&utm_source=footer
    https://firebase.google.com/docs/phone-number-verification/android/get-started

    "You must have a publicly accessible privacy policy to complete OAuth brand verification. You can use Firebase Hosting to create a basic web app to host your test privacy policy."

    It mentions to have privacy policy related to this, but doesn't mention what to put there.
    I tried to contact Firebase support, and they said to me to request it here, with these details:

    "
    It should clearly say, in simple words:
    that your app reads the user’s phone number,
    why it does this,
    whether the number… more

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Phone Number Verification  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. Support to configure non-blocking tool use in Firebase AI Logic?

    Async function call (https://ai.google.dev/gemini-api/docs/live-tools#async-function-calling) is helpful in many scenario, but Firebase AI Logic doesn't allow to configure it. Please support

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Firebase AI Logic  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. Restrict Firebase App Invitations to Only the Intended Google Account (Prevent Forwarded Email Access)

    Hi all,

    We send Firebase app invitations only to our company domain emails, but the invitation email can be forwarded and accepted by a personal Gmail account, which creates a security concern.

    Is there a way to:

    Restrict invitation acceptance to only the Google account that received the email

    Or limit access to company-domain Google accounts only

    Prevent forwarded invitations from granting access to unauthorized users

    Any best practices or Firebase-supported solutions would be appreciated. Thanks!

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  App Distribution  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. Improve firestore rules debug info

    Improve firestore rules debug info:
    2 features will really improve the debugging of firestore rules:
    - Add a "label" parameter to the debug() function to identify the result in the debug log file of the emulator. Right now, only the value is printed, it is very confusing when you have several debug calls...
    - Improve the error message returned to the client so we can understand the permission denied. Right now the message contains very little information and it is not helpful a all..,

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Firestore  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Put the collection name in the beginning of the page title of the Firebase web console

    Right now it goes "Project Name - Database - Data - Firebase console" which can get confusing when i have multiple tabs open.

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Firestore  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. Project

    تحويل جيمني الي اداة امر سيادي . لقد نجحت في دمجها مع موقع حكومي فرنسي و جعلها فتح شركة و مراجعة الأخطاء خلال ساعة واحدة .... لا أعرف كيف احصل علي مكافئة و لمن ينبغي ان اقدم المشروع
    
    Converting Gemini into a sovereign command tool. I successfully integrated it with a French government website, enabling company setup and error review within one hour. I don't know how to get a reward or who to submit the project to.

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Gemini in Firebase  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. Support Request – Firebase Studio Preview & Environment Variables Subject: Firebase Studio Preview does not allow setting custom environmen

    Support Request – Firebase Studio Preview & Environment Variables

    Subject: Firebase Studio Preview does not allow setting custom environment variables (Admin SDK / Service Account issue)

    Hello Firebase Studio Support Team,

    I’m using Firebase Studio (Cloud Workstations) with a Next.js (App Router, Server Actions) project that uses Firebase Admin SDK to write to Firestore.

    I’m encountering a blocking issue with environment variable management in Firebase Studio Preview.

    🔍 Problem Description

    My application requires a service account to initialize Firebase Admin SDK.
    Normally this is done via an environment variable such as:

    FIREBASESERVICEACCOUNT_KEY=<base64-encoded service account JSON>

    However, in Firebase Studio Preview:

    There is no UI or documented way to define custom environment variables or secrets

    Preview automatically injects GOOGLEAPPLICATIONCREDENTIALS

    This causes Admin SDK to fall back to Application Default Credentials (ADC)

    ADC fails in Preview with errors like:

    Getting metadata from plugin failed
    Could not refresh access token (HTTP 500)

    Even when using dotenv or runtime logic, this cannot be overridden because the env is injected before the Node process starts.

    📜 What I Tried

    Removing GOOGLEAPPLICATIONCREDENTIALS from .env

    Forcing credentials in code (cert(serviceAccount))

    Using dotenv

    Using Firebase CLI (functions:config:set)

    Restarting / rebuilding Preview

    Searching for Preview env / secrets configuration

    None of these allow injecting a custom env variable into the Preview runtime.

    ❓ Questions

    Is it currently supported to define custom environment variables or secrets for Firebase Studio Preview?

    If yes, where is this documented or configured?

    If not, is there a recommended workflow for projects using:

    Next.js Server Actions

    Firebase Admin SDK

    Firestore writes

    Is Preview intended only as a frontend-only viewer, not a backend runtime?

    🎯 Impact

    This limitation prevents:

    Testing Admin SDK logic

    Firestore write operations

    Any backend logic that depends on secure credentials

    At the moment, the only working solution is local development or Cloud Run/App Hosting, which defeats the purpose of Preview for full-stack apps.

    Thank you for your help.
    Clarification or documentation on this would be very valuable.

    Best regards,
    Murat

    Support Request – Firebase Studio Preview & Environment Variables

    Subject: Firebase Studio Preview does not allow setting custom environment variables (Admin SDK / Service Account issue)

    Hello Firebase Studio Support Team,

    I’m using Firebase Studio (Cloud Workstations) with a Next.js (App Router, Server Actions) project that uses Firebase Admin SDK to write to Firestore.

    I’m encountering a blocking issue with environment variable management in Firebase Studio Preview.

    🔍 Problem Description

    My application requires a service account to initialize Firebase Admin SDK.
    Normally this is done via an environment variable such as:

    FIREBASESERVICEACCOUNT_KEY=<base64-encoded service account JSON>

    However, in Firebase… more

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Firebase CLI  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. Add a CLI flag for hosting project previous release count option

    I have an ecommerce SAAS company where each client/tenant website is hosted on Firebase Hosting. We have over 80 websites hosted across six Firebase projects.

    We create each new site using the Firebase CLI:

    firebase hosting:sites:create [options] <siteId>

    The only options for this command are:

    --app <appId> specify an existing Firebase Web App ID
    -h, --help display help for command

    I'd like to request an additional option to set the "previous releases to keep", aka "previous release count".

    After I create a new site, I have to deploy the new website to Firebase hosting before I can set the previous release count on the Firebase Hosting website. The website won't let me set the release count before deploying my first release.

    If I can set this previous release count when creating the site, then I don't have to wait until after I complete these two required steps (plus remember to do it).

    If I forget to set the previous release count, then I'll end up with too many previous releases that I'm paying for that I'll never use.

    Basically, this would eliminate one of the many little annoying steps I need to do manually when launching a new tenant website.

    I have an ecommerce SAAS company where each client/tenant website is hosted on Firebase Hosting. We have over 80 websites hosted across six Firebase projects.

    We create each new site using the Firebase CLI:

    firebase hosting:sites:create [options] <siteId>

    The only options for this command are:

    --app <appId> specify an existing Firebase Web App ID
    -h, --help display help for command

    I'd like to request an additional option to set the "previous releases to keep", aka "previous release count".

    After I create a new site, I have to deploy the new website to Firebase hosting before I can set the previous… more

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Hosting  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. Don't require Github integration for App Hosting Backends

    I'm using Cloud Build and deploying to App Hosting using the CLI. We don't have an option when running firebase apphosting:backends:create to not connect a github repo, even though with the CLI deploy option the integration is not necessary. We're able to script setup of Hosting backends, but the github connection requirement in App Hosting disables our ability to script setup of our App Hosting Backends.

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  App Hosting  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating