如何将Firebase HTTP触发云函数改为向Google Pub/Sub发布消息？

Got it, let's refactor your existing HTTP-triggered Cloud Function to publish messages to Google Pub/Sub instead of sending emails. Here's how to do it clearly:

Prerequisites #

• First, make sure you've created a Pub/Sub topic in your Google Cloud project (same as your Firebase project). You can do this via the Google Cloud Console, or even programmatically, but manual creation is simpler for starters.
• If you're testing locally, install the Pub/Sub client library:

  npm install @google-cloud/pubsub
  

Updated Code #

Here's your modified function with Pub/Sub publishing logic replacing the email send code:

const functions = require('firebase-functions');
const { PubSub } = require('@google-cloud/pubsub');

// Initialize Pub/Sub client (uses default project credentials automatically in Cloud Functions)
const pubsub = new PubSub();
// Replace with YOUR Pub/Sub topic name
const topicName = 'your-topic-name';

exports.weeklyNotification = functions.https.onRequest(async (req, res) => {
  try {
    console.log('Publishing message to Pub/Sub');

    // Define your message data (can be any JSON/string payload you need)
    const messageData = {
      recipientEmail: '****@gmail.com',
      subject: 'Teste',
      content: 'Conteudo do email'
    };

    // Convert data to Buffer (required by Pub/Sub)
    const dataBuffer = Buffer.from(JSON.stringify(messageData));

    // Publish the message to the topic
    const messageId = await pubsub.topic(topicName).publish(dataBuffer);
    console.log(`Message published with ID: ${messageId}`);

    res.status(200).send(`Message published successfully! ID: ${messageId}`);
  } catch (error) {
    console.error('Error publishing message:', error);
    res.status(500).send(`Failed to publish message: ${error.message}`);
  }
});

Key Changes Explained #

• Pub/Sub Client Initialization: We import and initialize the Pub/Sub client, which automatically uses the Cloud Function's service account credentials (so you don't need to manually handle auth in production).
• Message Payload: Instead of mailOptions, we create a custom data object with whatever information you need to pass to downstream services (this can be anything, not just email-related data).
• Buffer Conversion: Pub/Sub requires message data to be a Buffer, so we stringify our JSON payload and convert it to a Buffer.
• Async/Await: I switched to async/await for cleaner error handling (you can still use .then() if you prefer, but async/await is more readable).
• Response Handling: We return appropriate HTTP status codes (200 for success, 500 for errors) along with meaningful messages.

Important Notes #

• Topic Existence: Ensure the topicName matches exactly the name of the topic you created in Google Cloud. If the topic doesn't exist, the publish call will throw an error.
• Permissions: The Cloud Function's default service account has the Pub/Sub Publisher role by default, but if you've modified permissions, make sure it has the pubsub.topics.publish permission for your topic.
• Testing: Deploy the function with firebase deploy --only functions, then send an HTTP request to the function's URL (you can get this from the Firebase Console after deployment) to trigger the Pub/Sub publish.

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