Re: [Firebase] firebase projects in a single account. What is the right design?

[Arthur Thompson]

Hi Sri Krishna,

The goal of the Firebase token was to allow the CLI to impersonate you without going through a sign in flow so the CLI could be used in CI/CD type workflows. A service account enables similar use cases but in a more secure and less disruptive manner.

If the Firebase token was sufficient for your use case then a service account should be a drop in replacement.

Using an organization structure will provide additional environment/user/team management features but those are not necessary to replicate the functionality provided by the Firebase token.

Hope this helps,

Arthur.

On Tue, Feb 13, 2024 at 6:35 PM Sri Krishna Vijayapuri <vsri...@gmail.com> wrote:

I am having a design question and I need help deciding what is the best architecture here. I am using firebase-cli and this command particularly "firebase login:ci" to get a long lived firebase token. I am setting FIREBASE_TOKEN parameter using this token and creating projects within my "vsri...@gmail.com" account. I recently saw a message saying the firebase tokens would be deprecated and I need to move to service account. I have a question here, to keep my setup of creating multiple firebase project inside a single account, should I use a service account or organization structure here? Should I be doing this using my own domain(srivijayapuri.cloud) here? Should I have my projects under an organization structure? Any help in this matter is highly appreciated. 

--
You received this message because you are subscribed to the Google Groups "Firebase Google Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firebase-tal...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/67206914-3adb-4d30-b8f3-0a11030edff0n%40googlegroups.com.