Is there real need for a Firebase Database extension? Isn't the existing Firestore extension already sufficient?

Well, depends on how you want to structure stuff. In principle, this could be part of the existing firebase extension (which also packs the auth stuff), it doesn't add any other transitive dependencies to that module. The module has another goal, which might validate the need for a separate module OTOH.

Lemme know what you prefer, either is fine with me

@jfbenckhuijsen my question was more of Firestore vs Firebase.
But I'm also a little concern about the cost to add a new extension if there already exist one with the same lib.

@jfbenckhuijsen my question was more of Firestore vs Firebase. But I'm also a little concern about the cost to add a new extension if there already exist one with the same lib.

Ah ok, clear. Firebase Realtime Database to my knowledge is a different product (with a different goal) than Firestore.

I can rewrite the extension to be part of the firebase-admin extension (this one has the same dependency). Downside is that the name would then not really fit the goal of that existing extension (we probably should rename it to -firebase instead of -firebase-admin, but that;s an backwards incompatible change ofc).

OK, let's keep both.

By the way, I plan to do a release soon so it's been available in the next Quarkus release but there is a test related to your recent changes that fails in the Quarkiverse CI which test this extension with the main branch of Quarkus.

If you can have a look it would be great otherwise I'll have a look later.

See https://github.com/quarkiverse/quarkus-google-cloud-services/actions/runs/12823020927/job/35756877903

OK, let's keep both.

By the way, I plan to do a release soon so it's been available in the next Quarkus release but there is a test related to your recent changes that fails in the Quarkiverse CI which test this extension with the main branch of Quarkus.

If you can have a look it would be great otherwise I'll have a look later.

See https://github.com/quarkiverse/quarkus-google-cloud-services/actions/runs/12823020927/job/35756877903

@loicmathieu Looking at the error, I think (but logging is quite limited) that the issue is caused by the fact that we made some changes to the build CI script, which aren't reflected in the Quarkus snapshot build (i.e. the NPM stuff and the current user stuff). I can have a go at creating a PR for that, but would probably need some help there as I'm not really familiar with those scripts and tests.

--> #743

I assume we consider this as finished and ready for merge then? (Other review issues were resolved).