如何将字符串通过Cloud Function上传至Firebase Cloud Storage

Hey there! Let's work through getting your Cloud Function up and running to upload that JSON string to Cloud Storage. Looking at your current code, there are a few key issues that are likely causing problems—let's break them down and fix them step by step.

Key Issues in Your Current Code #

• Missing proper Admin SDK initialization: In Cloud Functions, you need to use the official Firebase Admin SDK to interact with Cloud Storage, and your code has commented-out lines that hint at this but aren't fully implemented.
• Unnecessary data URL encoding: You're wrapping your JSON string in a data:text/json prefix, but Cloud Storage has simpler ways to upload raw JSON without this extra step.
• No returned Promise: Cloud Functions rely on promises to know when asynchronous operations (like file uploads) are complete. Your current code starts the upload but doesn't return the promise, which can cause the function to terminate early before the upload finishes.
• Messy variable structure: The commented-out lines and mixed variable names make it hard to follow the logic.

Corrected Cloud Function Code #

Let's start with an HTTP-triggered function (since it's a common use case for triggering uploads manually or from another service):

// Initialize Firebase Admin SDK (handled automatically when deployed to Cloud Functions; add this for local testing)
const admin = require('firebase-admin');
admin.initializeApp();

// HTTP-triggered function to upload JSON to Cloud Storage
exports.uploadJsonToStorage = async (req, res) => {
  try {
    // Replace this with how you actually get your exportObj (e.g., from request body, database, etc.)
    const exportObj = req.body.exportObj;
    
    // Get reference to your Cloud Storage bucket
    const bucket = admin.storage().bucket('your-bucket-name.appspot.com');
    const targetFileName = 'toctest.json';

    // Upload the JSON string directly with proper content type
    await bucket.file(targetFileName).save(JSON.stringify(exportObj), {
      contentType: 'application/json', // Ensures the file is recognized as JSON in Storage
      resumable: false // Disable resumable uploads for small files (faster)
    });

    console.log(`Successfully uploaded ${targetFileName} to Cloud Storage!`);
    res.status(200).send('Upload completed successfully');
  } catch (error) {
    console.error('Upload failed:', error);
    res.status(500).send(`Upload error: ${error.message}`);
  }
};

If You Need a Non-HTTP Trigger (e.g., Pub/Sub, Firestore) #

If your function is triggered by an event (like a new document in Firestore), here's a simplified version:

const admin = require('firebase-admin');
admin.initializeApp();

exports.uploadJsonOnEvent = async (event) => {
  try {
    // Example: Parse data from the trigger event (adjust based on your trigger type)
    const exportObj = JSON.parse(Buffer.from(event.data, 'base64').toString());
    
    const bucket = admin.storage().bucket('your-bucket-name.appspot.com');
    await bucket.file('toctest.json').save(JSON.stringify(exportObj), {
      contentType: 'application/json'
    });

    console.log('JSON file uploaded successfully!');
  } catch (error) {
    console.error('Upload failed:', error);
    throw error; // Let Cloud Functions know the execution failed
  }
};

What We Changed & Why #

1. Used async/await: Makes asynchronous code much easier to read and debug compared to nested .then() chains.
2. Direct file upload with save(): Instead of using putString with a data URL, we directly write the JSON string to the file. This is more efficient and avoids unnecessary encoding.
3. Set contentType: Ensures Cloud Storage recognizes the file as JSON, which is important for downstream uses (like serving it as a JSON API or parsing it later).
4. Returned proper promises/responses: For HTTP functions, we send clear success/failure responses. For event-triggered functions, we throw errors to signal execution failures to Cloud Functions.
5. Cleaned up initialization: The Admin SDK is properly initialized, which is required to access Cloud Storage from Cloud Functions.

Quick Deployment Notes #

• Make sure you've installed the required dependencies in your Cloud Functions project:

  npm install firebase-admin firebase-functions
  

• Replace your-bucket-name.appspot.com with your actual Cloud Storage bucket name.
• For local testing, use the Firebase Emulator Suite to avoid hitting production resources.

内容的提问来源于stack exchange，提问作者Connor Marting