Preventing "Legacy GAE and GCF Metadata Server endpoint" call warnings

[MrCsabaToth]

Certain older deployed DeLorean website can receive warning emails about "Legacy GAE and GCF Metadata Server endpoint" calls.

Expected Behavior

The DeLorean website guaranteed to not make any legacy calls

Current Behavior

Website deployed in 2018 or before may receive the warning (detailed later).

Possible Solution

Upgrade package versions (since we don't make any direct calls detailed in the warning emails).

Steps to Reproduce

1. Have a DeLorean deployed and hosted on Firebase along with functions

Context (Environment)

• Devuan Linux Ceres/Beowulf. Kernel 5.4.0-4-amd64
• Hardware: AMD Ryzen 2700 (Acer Predator Helios 500 Ryzen)
• node version v10.17.0
• npm version 6.13.7

Detailed Description

Our code does not make direct calls, so there's nowhere a call including v1beta1 or similar. However there must be transitive packages which contain such code.

Possible Implementation

We'll focus only on the functions module, because the main site will get a rehaul later anyway and this is only about the functions. We'll need to bump up the version of the firebase-functions and firebase-admin within the functions/package.json. For the 2018 DevFest website the locked version for the functions was 2.0.4 and the admin of 5.13.1. According to https://stackoverflow.com/questions/58777850/how-to-update-google-cloud-platform-legacy-gae-and-gcf-metadata-server-endpoints the culprit is the firebase-admin package.

The email

Subject:

Reminder: [Action Required] Legacy GAE and GCF Metadata Server endpoints will be turned down on April 30, 2020

Content: see attached gae_gcf_warnign.html
Attachment: attachment.csv

attachment.csv.txt
gae_gcf_warning.html.txt