Environment info

• firebase-tools version: All versions as of January 2025
• Platform: All platforms

Bug Description

The V2_REGION_TO_TIER mapping in src/deploy/functions/pricing.ts is missing several Cloud Functions regions that are officially supported by Google Cloud. This causes issues when deploying functions with minInstances to these regions.

Symptoms

1. With proper guards: The canCalculateMinInstanceCost() function returns false for missing regions, resulting in a generic warning message: "Cannot calculate the minimum monthly bill for this configuration"

2. Without guards: If monthlyMinInstanceCost() is called directly without checking canCalculateMinInstanceCost() first, it throws:

   TypeError: Cannot read properties of undefined (reading 'ram')
   

Root Cause

When deploying functions with minInstances to a region not in V2_REGION_TO_TIER:

1. V2_REGION_TO_TIER[endpoint.region] returns undefined
2. The code tries to access usage[endpoint.platform][tier].ram where tier is undefined
3. This causes the TypeError or triggers the fallback warning

Missing Regions

According to the official Firebase documentation, the following regions are missing:

Tier 1 regions (missing):

Tier 2 regions (missing):

Steps to Reproduce

1. Create a Cloud Function with minInstances configured for europe-west8 (Milan) region:

   import { onRequest } from "firebase-functions/v2/https";
   
   export const helloMilan = onRequest(
     {
       region: "europe-west8",
       minInstances: 1  // Required to trigger the bug
     },
     (req, res) => {
       res.send("Hello from Milan!");
     }
   );

2. Run firebase deploy --only functions

3. Observe the warning message about inability to calculate costs (or TypeError if guards are bypassed)

Note: The bug only manifests when minInstances is configured. Functions without minInstances are skipped in the cost calculation loop.

Expected Behavior

The deployment should complete successfully, with correct pricing tier calculation for all officially supported regions.

Proposed Solution

Add all missing regions to the V2_REGION_TO_TIER mapping with their correct pricing tiers as documented in the Cloud Functions pricing page.

Impact

• Affects users deploying to Milan, Johannesburg, Madrid, and other newer regions with minInstances
• Critical for Italian/European businesses requiring data residency in Italy
• Important for GDPR compliance for organizations in specific EU countries
• Prevents accurate cost estimation for these regions

Additional Context

I'm happy to submit a PR with the fix if this approach is approved.