Objectives
Write, deploy, and trigger an HTTP Cloud Function that accesses Spanner.
Costs
This document uses Spanner and Cloud Run, which are billable components of Google Cloud.
For information on the cost of using Spanner, see Spanner pricing.
For information on the cost of using Cloud Run, including free invocations, see Cloud Run pricing.
Before you begin
This document assumes you have a Spanner instance named
test-instance
and a database namedexample-db
that uses the music application schema. For instructions on creating an instance and database with the music application schema, see Quickstart using the console or the tutorials for Getting Started in Node.js, or Python.Enable the Cloud Run functions, Cloud Run, and Cloud Build APIs.
Install and initialize the gcloud CLI.
If you already have the gcloud CLI installed, update it by running the following command:
gcloud components update
Prepare your development environment:
Node.js
See the Node.js setup guide.
Python
See the Python setup guide.
Prepare the application
Clone the sample app repository to your local machine:
Node.js
git clone https://github.com/GoogleCloudPlatform/nodejs-docs-samples.git
Alternatively, you can download the sample as a zip file and extract it.
Python
git clone https://github.com/GoogleCloudPlatform/python-docs-samples.git
Alternatively, you can download the sample as a zip file and extract it.
Change to the directory that contains the Cloud Run functions sample code for accessing Spanner:
Node.js
cd nodejs-docs-samples/functions/spanner
Python
cd python-docs-samples/functions/spanner
Take a look at the sample code:
Node.js
Python
The function sends a SQL query to fetch all
Albums
data from your database. The function is executed when you make an HTTP request to the function's endpoint.
Deploy the function
To deploy the function with an HTTP trigger, run the following
command in the spanner
directory:
Node.js
gcloud beta run deploy nodejs-spanner-function \
--source . \
--region REGION \
--function spannerQuickstart \
--base-image RUNTIME_ID \
--log-http
Python
gcloud beta run deploy python-spanner-function \
--source . \
--region REGION \
--function spanner_read_data \
--base-image RUNTIME_ID \
--log-http
Replace:
REGION with the name of the Google Cloud region where you want to deploy your function (for example,
us-west1
).RUNTIME_ID with the appropriate runtime ID (for example,
nodejs22
). See Supported language runtimes and base images.
Function deployment might take up to two minutes.
Note the url
value returned when your function finishes deploying. You will
use it when you trigger the function.
You can view your deployed functions on the Cloud Run page in the Google Cloud console. You can also create and edit functions on that page, and get details and diagnostics for your functions.
Trigger the function
Make an HTTP request to your function:
curl URL
Replace URL with the URL value returned when your function finishes deploying.
You should see output that shows the results of the SQL query, assuming you worked through a Getting Started tutorial and populated the database:
SingerId: 2, AlbumId: 2, AlbumTitle: Forever Hold Your Peace
SingerId: 1, AlbumId: 2, AlbumTitle: Go, Go, Go
SingerId: 2, AlbumId: 1, AlbumTitle: Green
SingerId: 2, AlbumId: 3, AlbumTitle: Terrified
SingerId: 1, AlbumId: 1, AlbumTitle: Total Junk
You can also visit the function's URL in your browser to see the result of your SQL query.
Clean up
To avoid incurring additional charges to your Google Cloud account for the Spanner and Cloud Run functions resources used in this document:
Delete the instance:
gcloud CLI instances delete test-instance
Delete the Cloud Run service you deployed in this tutorial:
Node.js
gcloud run services delete nodejs-spanner-function
Python
gcloud run services delete python-spanner-function
What's next
- Learn more about writing Cloud Run functions.
- Learn more about deploying Cloud Run functions.
- Learn more about triggering Cloud Run functions.