Trigger functions from Pub/Sub using Eventarc
Stay organized with collections
Save and categorize content based on your preferences.
This tutorial demonstrates how to write and trigger an event-driven Cloud Run functions with a Pub/Sub trigger.
You can configure the routing of events, including the event source and the event target, by specifying filters for an Eventarc trigger. For the example in this tutorial, publishing a message to a Pub/Sub topic triggers the event, and a request is sent to your function in the form of an HTTP request.
If you are new to Pub/Sub and want to learn more, see the Pub/Sub documentation for quickstarts and key references.
Objectives
In this tutorial, you will:
Costs
In this document, you use the following billable components of Google Cloud:
To generate a cost estimate based on your projected usage,
use the pricing calculator.
Before you begin
Security constraints defined by your organization might prevent you from completing the following steps. For troubleshooting information, see Develop applications in a constrained Google Cloud environment.
- Sign in to your Google Cloud account. If you're new to Google Cloud, create an account to evaluate how our products perform in real-world scenarios. New customers also get 300ドル in free credits to run, test, and deploy workloads.
-
Install the Google Cloud CLI.
-
If you're using an external identity provider (IdP), you must first sign in to the gcloud CLI with your federated identity.
-
To initialize the gcloud CLI, run the following command:
gcloudinit
-
Create or select a Google Cloud project.
Roles required to select or create a project
- Select a project: Selecting a project doesn't require a specific IAM role—you can select any project that you've been granted a role on.
-
Create a project: To create a project, you need the Project Creator role
(
roles/resourcemanager.projectCreator), which contains theresourcemanager.projects.createpermission. Learn how to grant roles.
-
Create a Google Cloud project:
gcloud projects create PROJECT_ID
Replace
PROJECT_IDwith a name for the Google Cloud project you are creating. -
Select the Google Cloud project that you created:
gcloud config set project PROJECT_ID
Replace
PROJECT_IDwith your Google Cloud project name.
-
Verify that billing is enabled for your Google Cloud project.
-
Install the Google Cloud CLI.
-
If you're using an external identity provider (IdP), you must first sign in to the gcloud CLI with your federated identity.
-
To initialize the gcloud CLI, run the following command:
gcloudinit
-
Create or select a Google Cloud project.
Roles required to select or create a project
- Select a project: Selecting a project doesn't require a specific IAM role—you can select any project that you've been granted a role on.
-
Create a project: To create a project, you need the Project Creator role
(
roles/resourcemanager.projectCreator), which contains theresourcemanager.projects.createpermission. Learn how to grant roles.
-
Create a Google Cloud project:
gcloud projects create PROJECT_ID
Replace
PROJECT_IDwith a name for the Google Cloud project you are creating. -
Select the Google Cloud project that you created:
gcloud config set project PROJECT_ID
Replace
PROJECT_IDwith your Google Cloud project name.
-
Verify that billing is enabled for your Google Cloud project.
- If you are not using Cloud Shell, update the Google Cloud CLI
components and log in using your account:
gcloudcomponentsupdate gcloudauthlogin
- Enable the APIs:
gcloudservicesenableartifactregistry.googleapis.com\ cloudbuild.googleapis.com\ eventarc.googleapis.com\ run.googleapis.com\ logging.googleapis.com\ pubsub.googleapis.com
- Set the configuration variables used in this tutorial:
exportREGION=us-central1 gcloudconfigsetrun/region${REGION} gcloudconfigsetrun/platformmanaged gcloudconfigseteventarc/location${REGION}
- Create a service account:
SERVICE_ACCOUNT=eventarc-trigger-sa gcloudiamservice-accountscreate$SERVICE_ACCOUNT
If you are under a domain restriction organization policy restricting unauthenticated invocations for your project, you will need to access your deployed service as described under Testing private services.
Required roles
You or your administrator must grant the deployer account, the trigger identity, and optionally, the Pub/Sub service agent and the Cloud Storage service agent the following IAM roles.
Required roles for the deployer account
-
If you are the project creator, you are granted the basic Owner role (
roles/owner). By default, this Identity and Access Management (IAM) role includes the permissions necessary for full access to most Google Cloud resources and you can skip this step.If you are not the project creator, required permissions must be granted on the project to the appropriate principal. For example, a principal can be a Google Account (for end users) or a service account (for applications and compute workloads). For more information, see the Roles and permissions page for your event destination.
To get the permissions that you need to complete this tutorial, ask your administrator to grant you the following IAM roles on your project:
-
Cloud Run Source Developer (
roles/run.sourceDeveloper) -
Project IAM Admin (
roles/resourcemanager.projectIamAdmin) -
Service Account User (
roles/iam.serviceAccountUser) -
Service Usage Admin (
roles/serviceusage.serviceUsageAdmin) -
Logs View Accessor (
roles/logging.viewAccessor)
For more information about granting roles, see Manage access to projects, folders, and organizations.
You might also be able to get the required permissions through custom roles or other predefined roles.
Note that by default, Cloud Build permissions include permissions to upload and download Artifact Registry artifacts.
-
Cloud Run Source Developer (
Required roles for the trigger identity
Make note of the Compute Engine default service account as you will you attach it to an Eventarc trigger to represent the identity of the trigger for testing purposes. This service account is automatically created after enabling or using a Google Cloud service that uses Compute Engine, and with the following email format:
PROJECT_NUMBER-compute@developer.gserviceaccount.com
Replace
PROJECT_NUMBERwith your Google Cloud project number. You can find your project number on the Welcome page of the Google Cloud console or by running the following command:gcloudprojectsdescribePROJECT_ID--format='value(projectNumber)'
For production environments, we strongly recommend creating a new service account and granting it one or more IAM roles that contain the minimum permissions required and follow the principle of least privilege.
- By default, Cloud Run services are only callable by Project
Owners, Project Editors, and Cloud Run Admins and Invokers.
You can
control
access on a per-service basis; however, for testing purposes, grant the
Cloud Run
Invoker role (
run.invoker) on the Google Cloud project to the Compute Engine service account. This grants the role on all Cloud Run services and jobs in a project.gcloudprojectsadd-iam-policy-bindingPROJECT_ID\ --member=serviceAccount:PROJECT_NUMBER-compute@developer.gserviceaccount.com\ --role=roles/run.invoker
Note that if you create a trigger for an authenticated Cloud Run service without granting the Cloud Run Invoker role, the trigger is created successfully and is active. However, the trigger will not work as expected and a message similar to the following appears in the logs:
The request was not authenticated. Either allow unauthenticated invocations or set the proper Authorization header. - Grant the
Eventarc
Event Receiver role (
roles/eventarc.eventReceiver) on the project to the Compute Engine default service account so that the Eventarc trigger can receive events from event providers.gcloudprojectsadd-iam-policy-bindingPROJECT_ID\ --member=serviceAccount:PROJECT_NUMBER-compute@developer.gserviceaccount.com\ --role=roles/eventarc.eventReceiver
Optional role for the Cloud Storage service agent
- Before creating a trigger for direct events from Cloud Storage,
grant the Pub/Sub
Publisher role (
roles/pubsub.publisher) to the Cloud Storage service agent:SERVICE_ACCOUNT="$(gcloudstorageservice-agent--project=PROJECT_ID)" gcloudprojectsadd-iam-policy-bindingPROJECT_ID\ --member="serviceAccount:${SERVICE_ACCOUNT}"\ --role='roles/pubsub.publisher'
Optional role for the Pub/Sub service agent
- If you enabled the Cloud Pub/Sub service agent on or before April
8, 2021, to support authenticated Pub/Sub push requests, grant
the Service
Account Token Creator role (
roles/iam.serviceAccountTokenCreator) to the service agent. Otherwise, this role is granted by default:gcloudprojectsadd-iam-policy-bindingPROJECT_ID\ --member=serviceAccount:service-PROJECT_NUMBER@gcp-sa-pubsub.iam.gserviceaccount.com\ --role=roles/iam.serviceAccountTokenCreator
Create a Pub/Sub topic
In Cloud Run, Pub/Sub topics are not automatically created when you deploy a function. Before deploying your function, publish a message to this Pub/Sub topic to trigger the function:
gcloudpubsubtopicscreateYOUR_TOPIC_NAME
Prepare the application
Clone the sample app repository to your local machine:
Node.js
git clone https://github.com/GoogleCloudPlatform/nodejs-docs-samples.gitPython
git clone https://github.com/GoogleCloudPlatform/python-docs-samples.gitGo
git clone https://github.com/GoogleCloudPlatform/golang-samples.gitJava
git clone https://github.com/GoogleCloudPlatform/java-docs-samples.git.NET
git clone https://github.com/GoogleCloudPlatform/dotnet-docs-samples.gitRuby
git clone https://github.com/GoogleCloudPlatform/ruby-docs-samples.gitPHP
git clone https://github.com/GoogleCloudPlatform/php-docs-samples.gitChange to the directory that contains the sample code for accessing Pub/Sub:
Node.js
cd nodejs-docs-samples/functions/v2/helloPubSub/Python
cd python-docs-samples/functions/v2/pubsub/Go
cd golang-samples/functions/functionsv2/hellopubsub/Java
cd java-docs-samples/functions/v2/pubsub/.NET
cd dotnet-docs-samples/functions/helloworld/HelloPubSub/Ruby
cd ruby-docs-samples/functions/helloworld/pubsub/PHP
cd php-docs-samples/functions/helloworld_pubsub/Take a look at the sample code:
Node.js
constfunctions=require('@google-cloud/functions-framework'); // Register a CloudEvent callback with the Functions Framework that will // be executed when the Pub/Sub trigger topic receives a message. functions.cloudEvent('helloPubSub',cloudEvent=>{ // The Pub/Sub message is passed as the CloudEvent's data payload. constbase64name=cloudEvent.data.message.data; constname=base64name ?Buffer.from(base64name,'base64').toString() :'World'; console.log(`Hello, ${name}!`); });Python
importbase64 fromcloudevents.httpimport CloudEvent importfunctions_framework # Triggered from a message on a Cloud Pub/Sub topic. @functions_framework.cloud_event defsubscribe(cloud_event: CloudEvent) -> None: # Print out the data from Pub/Sub, to prove that it worked print( "Hello, " + base64.b64decode(cloud_event.data["message"]["data"]).decode() + "!" )Go
// Package helloworld provides a set of Cloud Functions samples. packagehelloworld import( "context" "fmt" "log" "github.com/GoogleCloudPlatform/functions-framework-go/functions" "github.com/cloudevents/sdk-go/v2/event" ) funcinit(){ functions.CloudEvent("HelloPubSub",helloPubSub) } // MessagePublishedData contains the full Pub/Sub message // See the documentation for more details: // https://cloud.google.com/eventarc/docs/cloudevents#pubsub typeMessagePublishedDatastruct{ MessagePubSubMessage } // PubSubMessage is the payload of a Pub/Sub event. // See the documentation for more details: // https://cloud.google.com/pubsub/docs/reference/rest/v1/PubsubMessage typePubSubMessagestruct{ Data[]byte`json:"data"` } // helloPubSub consumes a CloudEvent message and extracts the Pub/Sub message. funchelloPubSub(ctxcontext.Context,eevent.Event)error{ varmsgMessagePublishedData iferr:=e.DataAs(&msg);err!=nil{ returnfmt.Errorf("event.DataAs: %w",err) } name:=string(msg.Message.Data)// Automatically decoded from base64. ifname==""{ name="World" } log.Printf("Hello, %s!",name) returnnil }Java
importcom.google.cloud.functions.CloudEventsFunction; importcom.google.gson.Gson; importfunctions.eventpojos.PubSubBody; importio.cloudevents.CloudEvent; importjava.nio.charset.StandardCharsets; importjava.util.Base64; importjava.util.logging.Logger; publicclass SubscribeToTopicimplementsCloudEventsFunction{ privatestaticfinalLoggerlogger=Logger.getLogger(SubscribeToTopic.class.getName()); @Override publicvoidaccept(CloudEventevent){ // The Pub/Sub message is passed as the CloudEvent's data payload. if(event.getData()!=null){ // Extract Cloud Event data and convert to PubSubBody StringcloudEventData=newString(event.getData().toBytes(),StandardCharsets.UTF_8); Gsongson=newGson(); PubSubBodybody=gson.fromJson(cloudEventData,PubSubBody.class); // Retrieve and decode PubSub message data StringencodedData=body.getMessage().getData(); StringdecodedData= newString(Base64.getDecoder().decode(encodedData),StandardCharsets.UTF_8); logger.info("Hello, "+decodedData+"!"); } } }.NET
usingCloudNative.CloudEvents; usingGoogle.Cloud.Functions.Framework; usingGoogle.Events.Protobuf.Cloud.PubSub.V1; usingMicrosoft.Extensions.Logging; usingSystem.Threading; usingSystem.Threading.Tasks; namespaceHelloPubSub; publicclassFunction:ICloudEventFunction<MessagePublishedData> { privatereadonlyILogger_logger; publicFunction(ILogger<Function>logger)=> _logger=logger; publicTaskHandleAsync(CloudEventcloudEvent,MessagePublishedDatadata,CancellationTokencancellationToken) { stringnameFromMessage=data.Message?.TextData; stringname=string.IsNullOrEmpty(nameFromMessage)?"world":nameFromMessage; _logger.LogInformation("Hello {name}",name); returnTask.CompletedTask; } }Ruby
require"functions_framework" require"base64" FunctionsFramework.cloud_event"hello_pubsub"do|event| # The event parameter is a CloudEvents::Event::V1 object. # See https://cloudevents.github.io/sdk-ruby/latest/CloudEvents/Event/V1.html name=Base64.decode64event.data["message"]["data"]rescue"World" # A cloud_event function does not return a response, but you can log messages # or cause side effects such as sending additional events. logger.info"Hello, #{name}!" endPHP
use CloudEvents\V1\CloudEventInterface; use Google\CloudFunctions\FunctionsFramework; // Register the function with Functions Framework. // This enables omitting the `FUNCTIONS_SIGNATURE_TYPE=cloudevent` environment // variable when deploying. The `FUNCTION_TARGET` environment variable should // match the first parameter. FunctionsFramework::cloudEvent('helloworldPubsub', 'helloworldPubsub'); function helloworldPubsub(CloudEventInterface $event): void { $log = fopen(getenv('LOGGER_OUTPUT') ?: 'php://stderr', 'wb'); $cloudEventData = $event->getData(); $pubSubData = base64_decode($cloudEventData['message']['data']); $name = $pubSubData ? htmlspecialchars($pubSubData) : 'World'; fwrite($log, "Hello, $name!" . PHP_EOL); }
Deploy an event-driven function
To deploy the function, run the following command in the directory that contains the sample code:
Node.js
gcloud run deploy FUNCTION \
--source . \
--function helloPubSub \
--base-image BASE_IMAGE \
Replace:
- FUNCTION with the name of the function you are deploying. If you omit this parameter, you will be prompted to enter a name when you run the command.
- BASE_IMAGE with the base image environment for your function,
for example,
nodejs24. For more details about base images and the packages included in each image, see Supported language runtimes and base images.
Python
gcloud run deploy FUNCTION \
--source . \
--function subscribe \
--base-image BASE_IMAGE \
Replace:
- FUNCTION with the name of the function you are deploying. If you omit this parameter, you will be prompted to enter a name when you run the command.
- BASE_IMAGE with the base image environment for your function,
for example,
python313. For more details about base images and the packages included in each image, see Supported language runtimes and base images.
Go
gcloud run deploy FUNCTION \
--source . \
--function HelloPubSub \
--base-image BASE_IMAGE \
Replace:
- FUNCTION with the name of the function you are deploying. If you omit this parameter, you will be prompted to enter a name when you run the command.
- BASE_IMAGE with the base image environment for your function,
for example,
go125. For more details about base images and the packages included in each image, see Supported language runtimes and base images.
Java
gcloud run deploy FUNCTION \
--source . \
--function functions.SubscribeToTopic \
--base-image BASE_IMAGE \
Replace:
- FUNCTION with the name of the function you are deploying. If you omit this parameter, you will be prompted to enter a name when you run the command.
- BASE_IMAGE with the base image environment for your function,
for example,
java21. For more details about base images and the packages included in each image, see Supported language runtimes and base images.
.NET
gcloud run deploy FUNCTION \
--source . \
--function HelloPubSub.Function \
--base-image BASE_IMAGE \
Replace:
- FUNCTION with the name of the function you are deploying. If you omit this parameter, you will be prompted to enter a name when you run the command.
- BASE_IMAGE with the base image environment for your function,
for example,
dotnet8. For more details about base images and the packages included in each image, see Supported language runtimes and base images.
Ruby
gcloud run deploy FUNCTION \
--source . \
--function hello_pubsub \
--base-image BASE_IMAGE \
Replace:
- FUNCTION with the name of the function you are deploying. If you omit this parameter, you will be prompted to enter a name when you run the command.
- BASE_IMAGE with the base image environment for your function,
for example,
ruby34. For more details about base images and the packages included in each image, see Supported language runtimes and base images.
PHP
gcloud run deploy FUNCTION \
--source . \
--function helloworldPubsub \
--base-image BASE_IMAGE \
Replace:
- FUNCTION with the name of the function you are deploying. If you omit this parameter, you will be prompted to enter a name when you run the command.
- BASE_IMAGE with the base image environment for your function,
for example,
php84. For more details about base images and the packages included in each image, see Supported language runtimes and base images.
If you are prompted to create a repository in the specified region, respond by
pressing y.
When the deployment is complete, the Google Cloud CLI displays a URL where
the service is running.
Create an Eventarc trigger
To deploy the function with a Pub/Sub trigger, run the following command in the directory that contains the sample code:
Create an Eventarc Pub/Sub trigger:
gcloudeventarctriggerscreateTRIGGER_NAME\ --location=${REGION}\ --destination-run-service=FUNCTION\ --destination-run-region=${REGION}\ --event-filters="type=google.cloud.pubsub.topic.v1.messagePublished"\ --service-account=PROJECT_NUMBER-compute@developer.gserviceaccount.com
Replace:
- TRIGGER_NAME with the name for your trigger.
- FUNCTION with the name of your function.
- PROJECT_NUMBER with your Google Cloud project number.
Note that when creating an Eventarc trigger for the first time in a Google Cloud project, there might be a delay in provisioning the Eventarc service agent. This issue can usually be resolved by attempting to create the trigger again. For more information, see Permission denied errors.
Confirm that the trigger was successfully created. Note that although your trigger is created immediately, it can take up to two minutes for a trigger to be fully functional.
gcloudeventarctriggerslist--location=${REGION}
The output should be similar to the following:
NAME: helloworld-events TYPE: google.cloud.pubsub.topic.v1.messagePublished DESTINATION: Cloud Run service: helloworld-events ACTIVE: Yes LOCATION: us-central1
Trigger the function
To test the Pub/Sub function:
Assign the topic to a variable:
TOPIC_ID=$(gcloud eventarc triggers describe TRIGGER_NAME --location $REGION --format='value(transport.pubsub.topic)')Publish a message to the topic:
gcloud pubsub topics publish $TOPIC_ID --message="Hello World"
The Cloud Run service logs the body of the incoming message. You can view this in the Logs section of your Cloud Run instance:
- Navigate to the Google Cloud console.
- Click the function.
Select the Logs tab.
Logs might take a few moments to appear. If you don't see them immediately, check again after a few moments.
Look for the "Hello World!" message.
Clean up
If you created a new project for this tutorial, delete the project. If you used an existing project and want to keep it without the changes added in this tutorial, delete the resources created for the tutorial.
Delete the project
The easiest way to eliminate billing is to delete the project that you created for the tutorial.
To delete the project:
- In the Google Cloud console, go to the Manage resources page.
- In the project list, select the project that you want to delete, and then click Delete.
- In the dialog, type the project ID, and then click Shut down to delete the project.
Delete tutorial resources
Delete the Cloud Run service you deployed in this tutorial:
gcloudrunservicesdeleteSERVICE_NAME
Where
SERVICE_NAMEis your chosen service name.You can also delete Cloud Run services from the Google Cloud console.
Remove any gcloud CLI default configurations you added during the tutorial setup.
For example:
gcloud config unset run/regionor
gcloud config unset projectDelete other Google Cloud resources created in this tutorial:
- Delete the Eventarc trigger:
Replacegcloud eventarc triggers delete TRIGGER_NAME
TRIGGER_NAMEwith the name of your trigger.
- Delete the Eventarc trigger: