FireBase sendMessage Function 更新到 v1 Google Cloud Endpoint

Question

So... this morning... I got an email saying:

Our records show that you own projects with App Engine applications or Cloud Functions that are still calling the pre-GA v0.1 and v1beta1 endpoints of the App Engine and Cloud Functions metadata server.

We're writing to let you know that these legacy endpoints are scheduled to be turned down on April 30, 2020. After April 30, 2020, requests to the v0.1 and v1beta1 endpoints will no longer be supported, and may return HTTP 404 NOT FOUND responses.

I'm only using Firebase Functions to send messages... and the email went on to identify my sendMessage function as the culprit. But I can't... for the life of me... figure out WHERE I need to update the endpoints. My sendMessage function is as follows:

exports.sendMessage = functions.database.ref('/messages/{receiverUid}/{senderUid}/{msgId}')
    .onWrite(async (change, context) => {
      const message = change.after.val().body;
      const receiverUid = change.after.val().receiverUid;
      const senderUid = change.after.val().senderUid;
      const msgId = change.after.val().msgId;
      if (!change.after.val()) {
        return console.log('Sender ', senderUid, 'receiver ', receiverUid, 'message ', message);
      }
      console.log('We have a new message: ', message, 'for: ', receiverUid);

I've tried following some of the Curl suggestions from this link: https://cloud.google.com/compute/docs/migrating-to-v1-metadata-server

...but every time I try one of them I get:

curl: (6) Couldn't resolve host 'metadata.google.internal'

So... at this point... I have no idea what it is I'm supposed to change or where I'm supposed to look. Any help would be appreciated.

Answer 1

I had this same problem, and didn't see any of the libraries I was using listed here .

In my case, the culprit turned out to be firebase-admin . I was using version 7.3.0, and I found this gem:

$ grep -rni "computeMetadata/" *
firebase-admin/lib/auth/credential.js:30:var GOOGLE_METADATA_SERVICE_PATH = '/computeMetadata/v1beta1/instance/service-accounts/default/token';

So, I updated my Cloud Functions libraries as shown here :

npm install firebase-functions@latest --save
npm install firebase-admin@latest --save-exact

and then, voila!

$ grep -rni "computeMetadata/" *
node_modules/firebase-admin/lib/auth/credential.js:30:var GOOGLE_METADATA_SERVICE_PATH = '/computeMetadata/v1/instance/service-accounts/default/token';

Then I redeployed and problem solved.

Answer 2

I searched at the https://github.com/firebase/firebase-functions repo latest version (3.3.0), and I found the file: spec/fixtures/https.ts. Inside this file there are some mock functions, which use the old: /computeMetadata/v1beta1 endpoint.

This might mean that firebase-functions modules package should be updated to use the /computeMetadata/v1 endpoint instead.

Answer 3

Fwiw I found this old dependency in package.json was dragging in other very old packages:

"@google-cloud/functions-emulator": "^1.0.0-beta.6",

In particular it brought in gcs-resumable-upload v 0.10.2, which is below the v 0.13.0 recommended by google (see https://cloud.google.com/compute/docs/migrating-to-v1-metadata-server#apps-to-update ). Probably others too.

The fix was to either:

• remove @google-cloud/functions-emulator , or
• switch to its modern replacement, @google-cloud/functions-framework