devconsole | Custom Developer Console | Command Line Interface library

This is essentially @Ladicek's comment:

[The behaviour] is intentional, but there are discussions it should be off by default. In any case, there's a configuration property to switch it off.

I was also able to locate the BuildExtension that does the magic: It is located inside io.quarkus.arc.deployment.devconsole.ArcDevConsoleProcessor.

It's an authentication issue. Just logout firebase CLI and log in again.

To logout :

Moving details from comments section to full answer

1. The correct URL to access Cloud Console is https://console.cloud.google.com and then you select Datastore from the drop down menu on the left

2. OP was using an old url - https://console.*developers*.google.com/

I followed the medium post that you shared. NOTE (where my_project_id is, you have to set your project id).

First I created the project (My user has an owner role in the project) and the environment.

change fb alias in cli to project name + change

Instead of using firebase I used a npm package called react-google-login, which provides the access_token. I used that access token to authorize the YouTube API, which worked.

https://www.npmjs.com/package/react-google-login

The first part of the solution was to read the response carefully. It containes the following link https://developers.google.com/identity/sign-in/web/devconsole-project.

Then I had to understand that if you are using the google-identitiy-toolkit you kind of left the firebase-realm and must append the api-key generated in the GC-console (not the firebase-key!) (https://console.cloud.google.com/apis/credentials) to the URL used to fetch the data like this:

The Actions on Google / Actions Builder platform is not designed to be used outside of the Google Assistant environment. If you want a way to programmatically match intents or call an API, you should use Dialogflow and their APIs.

As explained in the Firestore REST API documentation:

For authentication, the Cloud Firestore REST API accepts either a Firebase Authentication ID token or a Google Identity OAuth 2.0 token.

The token you provide affects your request's authorization:

• Use Firebase ID tokens to authenticate requests from your application's users. For these requests, Cloud Firestore uses Cloud Firestore Security Rules to determine if a request is authorized.

• Use a Google Identity OAuth 2.0 token and a service account to authenticate requests from your application, such as requests for database administration. For these requests, Cloud Firestore uses Identity and Access Management (IAM) to determine if a request is authorized.

The doc then explains how to get a Firebase ID token or how to generate an access token by using a service account. You have to decide which approach to choose depending on your exact case (are you interacting with Firestore only via the REST API? Do you mix calls through a Client SDK -e.g. to the Firebase Auth service- with call to the API?).

After you obtain either a Firebase ID token or a Google Identity OAuth 2.0 token, pass it to the Cloud Firestore endpoints as an Authorization header set to Bearer {YOUR_TOKEN}.

Below is an example of getting a Firebase ID Token via the JS SDK, then build the header and call a Firestore API endpoint (runQuery for querying a collection) via the axios library: