Cloud Storage Tutorial (1st gen)


This simple tutorial demonstrates writing, deploying, and triggering an Event-Driven Cloud Run function with a Cloud Storage trigger to respond to Cloud Storage events.

If you're looking for code samples for using Cloud Storage itself, visit the Google Cloud sample browser .

Objectives

Costs

In this document, you use the following billable components of Google Cloud:

  • Cloud Run functions
  • Cloud Storage

To generate a cost estimate based on your projected usage, use the pricing calculator .

New Google Cloud users might be eligible for a free trial .

Before you begin

  1. 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.
  2. In the Google Cloud console, on the project selector page, select or create a Google Cloud project.

    Go to project selector

  3. Verify that billing is enabled for your Google Cloud project .

  4. Enable the Cloud Functions, Cloud Build, Cloud Storage, and Eventarc APIs.

    Enable the APIs

  5. Install the Google Cloud CLI.

  6. If you're using an external identity provider (IdP), you must first sign in to the gcloud CLI with your federated identity .

  7. To initialize the gcloud CLI, run the following command:

    gcloud  
    init
  8. In the Google Cloud console, on the project selector page, select or create a Google Cloud project.

    Go to project selector

  9. Verify that billing is enabled for your Google Cloud project .

  10. Enable the Cloud Functions, Cloud Build, Cloud Storage, and Eventarc APIs.

    Enable the APIs

  11. Install the Google Cloud CLI.

  12. If you're using an external identity provider (IdP), you must first sign in to the gcloud CLI with your federated identity .

  13. To initialize the gcloud CLI, run the following command:

    gcloud  
    init
  14. If you already have the gcloud CLI installed, update it by running the following command:

    gcloud components update
  15. Prepare your development environment:

Preparing the application

  1. Create a Cloud Storage bucket to upload a test file, where YOUR_TRIGGER_BUCKET_NAME is a globally unique bucket name:

    gcloud  
    storage  
    buckets  
    create  
    gs:// YOUR_TRIGGER_BUCKET_NAME 
    
  2. 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.

    Go

    git clone https://github.com/GoogleCloudPlatform/golang-samples.git

    Alternatively, you can download the sample as a zip file and extract it.

    Java

    git clone https://github.com/GoogleCloudPlatform/java-docs-samples.git

    Alternatively, you can download the sample as a zip file and extract it.

    Ruby

    git clone https://github.com/GoogleCloudPlatform/ruby-docs-samples.git

    Alternatively, you can download the sample as a zip file and extract it.

  3. Change to the directory that contains the Cloud Run functions sample code:

    Node.js

    cd nodejs-docs-samples/functions/helloworld/

    Python

    cd python-docs-samples/functions/helloworld/

    Go

    cd golang-samples/functions/helloworld/

    Java

    cd java-docs-samples/functions/helloworld/hello-gcs/

    Ruby

    cd ruby-docs-samples/functions/helloworld/storage/

Deploying and triggering the function

Cloud Storage functions are based on Pub/Sub notifications from Cloud Storage and support similar event types:

The following sections describe how to deploy and trigger a function for each of these event types.

Object Finalize

Object finalize events trigger when a "write" of a Cloud Storage Object is successfully finalized. In particular, this means that creating a new object or overwriting an existing object triggers this event. Archive and metadata update operations are ignored by this trigger.

Object Finalize: deploying the function

Take a look at the sample function, which handles Cloud Storage events:

Node.js

  /** 
 * Generic background Cloud Function to be triggered by Cloud Storage. 
 * This sample works for all Cloud Storage CRUD operations. 
 * 
 * @param {object} file The Cloud Storage file metadata. 
 * @param {object} context The event metadata. 
 */ 
 exports 
 . 
 helloGCS 
  
 = 
  
 ( 
 file 
 , 
  
 context 
 ) 
  
 = 
>  
 { 
  
 console 
 . 
 log 
 ( 
 `  Event: 
 ${ 
 context 
 . 
 eventId 
 } 
 ` 
 ); 
  
 console 
 . 
 log 
 ( 
 `  Event Type: 
 ${ 
 context 
 . 
 eventType 
 } 
 ` 
 ); 
  
 console 
 . 
 log 
 ( 
 `  Bucket: 
 ${ 
 file 
 . 
 bucket 
 } 
 ` 
 ); 
  
 console 
 . 
 log 
 ( 
 `  File: 
 ${ 
 file 
 . 
 name 
 } 
 ` 
 ); 
  
 console 
 . 
 log 
 ( 
 `  Metageneration: 
 ${ 
 file 
 . 
 metageneration 
 } 
 ` 
 ); 
  
 console 
 . 
 log 
 ( 
 `  Created: 
 ${ 
 file 
 . 
 timeCreated 
 } 
 ` 
 ); 
  
 console 
 . 
 log 
 ( 
 `  Updated: 
 ${ 
 file 
 . 
 updated 
 } 
 ` 
 ); 
 }; 
 

Python

  def 
  
 hello_gcs 
 ( 
 event 
 , 
 context 
 ): 
  
 """Background Cloud Function to be triggered by Cloud Storage. 
 This generic function logs relevant data when a file is changed, 
 and works for all Cloud Storage CRUD operations. 
 Args: 
 event (dict):  The dictionary with data specific to this type of event. 
 The `data` field contains a description of the event in 
 the Cloud Storage `object` format described here: 
 https://cloud.google.com/storage/docs/json_api/v1/objects#resource 
 context (google.cloud.functions.Context): Metadata of triggering event. 
 Returns: 
 None; the output is written to Cloud Logging 
 """ 
 print 
 ( 
 f 
 "Event ID: 
 { 
 context 
 . 
 event_id 
 } 
 " 
 ) 
 print 
 ( 
 f 
 "Event type: 
 { 
 context 
 . 
 event_type 
 } 
 " 
 ) 
 print 
 ( 
 "Bucket: 
 {} 
 " 
 . 
 format 
 ( 
 event 
 [ 
 "bucket" 
 ])) 
 print 
 ( 
 "File: 
 {} 
 " 
 . 
 format 
 ( 
 event 
 [ 
 "name" 
 ])) 
 print 
 ( 
 "Metageneration: 
 {} 
 " 
 . 
 format 
 ( 
 event 
 [ 
 "metageneration" 
 ])) 
 print 
 ( 
 "Created: 
 {} 
 " 
 . 
 format 
 ( 
 event 
 [ 
 "timeCreated" 
 ])) 
 print 
 ( 
 "Updated: 
 {} 
 " 
 . 
 format 
 ( 
 event 
 [ 
 "updated" 
 ])) 
 

Go

  // Package helloworld provides a set of Cloud Functions samples. 
 package 
  
 helloworld 
 import 
  
 ( 
  
 "context" 
  
 "fmt" 
  
 "log" 
  
 "time" 
  
 "cloud.google.com/go/functions/metadata" 
 ) 
 // GCSEvent is the payload of a GCS event. 
 type 
  
 GCSEvent 
  
 struct 
  
 { 
  
 Kind 
  
 string 
  
 `json:"kind"` 
  
 ID 
  
 string 
  
 `json:"id"` 
  
 SelfLink 
  
 string 
  
 `json:"selfLink"` 
  
 Name 
  
 string 
  
 `json:"name"` 
  
 Bucket 
  
 string 
  
 `json:"bucket"` 
  
 Generation 
  
 string 
  
 `json:"generation"` 
  
 Metageneration 
  
 string 
  
 `json:"metageneration"` 
  
 ContentType 
  
 string 
  
 `json:"contentType"` 
  
 TimeCreated 
  
 time 
 . 
 Time 
  
 `json:"timeCreated"` 
  
 Updated 
  
 time 
 . 
 Time 
  
 `json:"updated"` 
  
 TemporaryHold 
  
 bool 
  
 `json:"temporaryHold"` 
  
 EventBasedHold 
  
 bool 
  
 `json:"eventBasedHold"` 
  
 RetentionExpirationTime 
  
 time 
 . 
 Time 
  
 `json:"retentionExpirationTime"` 
  
 StorageClass 
  
 string 
  
 `json:"storageClass"` 
  
 TimeStorageClassUpdated 
  
 time 
 . 
 Time 
  
 `json:"timeStorageClassUpdated"` 
  
 Size 
  
 string 
  
 `json:"size"` 
  
 MD5Hash 
  
 string 
  
 `json:"md5Hash"` 
  
 MediaLink 
  
 string 
  
 `json:"mediaLink"` 
  
 ContentEncoding 
  
 string 
  
 `json:"contentEncoding"` 
  
 ContentDisposition 
  
 string 
  
 `json:"contentDisposition"` 
  
 CacheControl 
  
 string 
  
 `json:"cacheControl"` 
  
 Metadata 
  
 map 
 [ 
 string 
 ] 
 interface 
 {} 
  
 `json:"metadata"` 
  
 CRC32C 
  
 string 
  
 `json:"crc32c"` 
  
 ComponentCount 
  
 int 
  
 `json:"componentCount"` 
  
 Etag 
  
 string 
  
 `json:"etag"` 
  
 CustomerEncryption 
  
 struct 
  
 { 
  
 EncryptionAlgorithm 
  
 string 
  
 `json:"encryptionAlgorithm"` 
  
 KeySha256 
  
 string 
  
 `json:"keySha256"` 
  
 } 
  
 KMSKeyName 
  
 string 
  
 `json:"kmsKeyName"` 
  
 ResourceState 
  
 string 
  
 `json:"resourceState"` 
 } 
 // HelloGCS consumes a(ny) GCS event. 
 func 
  
 HelloGCS 
 ( 
 ctx 
  
 context 
 . 
 Context 
 , 
  
 e 
  
 GCSEvent 
 ) 
  
 error 
  
 { 
  
 meta 
 , 
  
 err 
  
 := 
  
 metadata 
 . 
  FromContext 
 
 ( 
 ctx 
 ) 
  
 if 
  
 err 
  
 != 
  
 nil 
  
 { 
  
 return 
  
 fmt 
 . 
 Errorf 
 ( 
 "metadata.FromContext: %w" 
 , 
  
 err 
 ) 
  
 } 
  
 log 
 . 
 Printf 
 ( 
 "Event ID: %v\n" 
 , 
  
 meta 
 . 
 EventID 
 ) 
  
 log 
 . 
 Printf 
 ( 
 "Event type: %v\n" 
 , 
  
 meta 
 . 
 EventType 
 ) 
  
 log 
 . 
 Printf 
 ( 
 "Bucket: %v\n" 
 , 
  
 e 
 . 
 Bucket 
 ) 
  
 log 
 . 
 Printf 
 ( 
 "File: %v\n" 
 , 
  
 e 
 . 
 Name 
 ) 
  
 log 
 . 
 Printf 
 ( 
 "Metageneration: %v\n" 
 , 
  
 e 
 . 
 Metageneration 
 ) 
  
 log 
 . 
 Printf 
 ( 
 "Created: %v\n" 
 , 
  
 e 
 . 
 TimeCreated 
 ) 
  
 log 
 . 
 Printf 
 ( 
 "Updated: %v\n" 
 , 
  
 e 
 . 
 Updated 
 ) 
  
 return 
  
 nil 
 } 
 

Java

  import 
  
 com.google.cloud.functions.BackgroundFunction 
 ; 
 import 
  
 com.google.cloud.functions.Context 
 ; 
 import 
  
 functions.eventpojos.GcsEvent 
 ; 
 import 
  
 java.util.logging.Logger 
 ; 
 /** 
 * Example Cloud Storage-triggered function. 
 * This function can process any event from Cloud Storage. 
 */ 
 public 
  
 class 
 HelloGcs 
  
 implements 
  
 BackgroundFunction<GcsEvent> 
  
 { 
  
 private 
  
 static 
  
 final 
  
 Logger 
  
 logger 
  
 = 
  
 Logger 
 . 
 getLogger 
 ( 
 HelloGcs 
 . 
 class 
 . 
 getName 
 ()); 
  
 @Override 
  
 public 
  
 void 
  
 accept 
 ( 
 GcsEvent 
  
 event 
 , 
  
 Context 
  
 context 
 ) 
  
 { 
  
 logger 
 . 
 info 
 ( 
 "Event: " 
  
 + 
  
 context 
 . 
 eventId 
 ()); 
  
 logger 
 . 
 info 
 ( 
 "Event Type: " 
  
 + 
  
 context 
 . 
 eventType 
 ()); 
  
 logger 
 . 
 info 
 ( 
 "Bucket: " 
  
 + 
  
 event 
 . 
 getBucket 
 ()); 
  
 logger 
 . 
 info 
 ( 
 "File: " 
  
 + 
  
 event 
 . 
 getName 
 ()); 
  
 logger 
 . 
 info 
 ( 
 "Metageneration: " 
  
 + 
  
 event 
 . 
 getMetageneration 
 ()); 
  
 logger 
 . 
 info 
 ( 
 "Created: " 
  
 + 
  
 event 
 . 
 getTimeCreated 
 ()); 
  
 logger 
 . 
 info 
 ( 
 "Updated: " 
  
 + 
  
 event 
 . 
 getUpdated 
 ()); 
  
 } 
 } 
 

Ruby

  require 
  
 "functions_framework" 
 FunctionsFramework 
 . 
 cloud_event 
  
 "hello_gcs" 
  
 do 
  
 | 
 event 
 | 
  
 # This function supports all Cloud Storage events. 
  
 # The `event` parameter is a CloudEvents::Event::V1 object. 
  
 # See https://cloudevents.github.io/sdk-ruby/latest/CloudEvents/Event/V1.html 
  
 payload 
  
 = 
  
 event 
 . 
 data 
  
 logger 
 . 
 info 
  
 "Event: 
 #{ 
 event 
 . 
 id 
 } 
 " 
  
 logger 
 . 
 info 
  
 "Event Type: 
 #{ 
 event 
 . 
 type 
 } 
 " 
  
 logger 
 . 
 info 
  
 "Bucket: 
 #{ 
 payload 
 [ 
 'bucket' 
 ] 
 } 
 " 
  
 logger 
 . 
 info 
  
 "File: 
 #{ 
 payload 
 [ 
 'name' 
 ] 
 } 
 " 
  
 logger 
 . 
 info 
  
 "Metageneration: 
 #{ 
 payload 
 [ 
 'metageneration' 
 ] 
 } 
 " 
  
 logger 
 . 
 info 
  
 "Created: 
 #{ 
 payload 
 [ 
 'timeCreated' 
 ] 
 } 
 " 
  
 logger 
 . 
 info 
  
 "Updated: 
 #{ 
 payload 
 [ 
 'updated' 
 ] 
 } 
 " 
 end 
 

To deploy the function, run the following command in the directory where the sample code is located:

Node.js

gcloud functions deploy helloGCS \
--runtime nodejs20 \
--trigger-resource YOUR_TRIGGER_BUCKET_NAME \
--trigger-event google.storage.object.finalize

Use the --runtime flag to specify the runtime ID of a supported Node.js version to run your function.

Python

gcloud functions deploy hello_gcs \
--runtime python312 \
--trigger-resource YOUR_TRIGGER_BUCKET_NAME \
--trigger-event google.storage.object.finalize

Use the --runtime flag to specify the runtime ID of a supported Python version to run your function.

Go

gcloud functions deploy HelloGCS \
--runtime go121 \
--trigger-resource YOUR_TRIGGER_BUCKET_NAME \
--trigger-event google.storage.object.finalize

Use the --runtime flag to specify the runtime ID of a supported Go version to run your function.

Java

gcloud functions deploy java-gcs-function \
--entry-point functions.HelloGcs \
--runtime java17 \
--memory 512MB \
--trigger-resource YOUR_TRIGGER_BUCKET_NAME \
--trigger-event google.storage.object.finalize

Use the --runtime flag to specify the runtime ID of a supported Java version to run your function.

Ruby

gcloud  
functions  
deploy  
hello_gcs  
--runtime  
ruby33  
 \
-
-trigger-resource YOUR_TRIGGER_BUCKET_NAME \
-
-trigger-event google.storage.object.finalize

Use the --runtime flag to specify the runtime ID of a supported Ruby version to run your function.

where YOUR_TRIGGER_BUCKET_NAME is the name of the Cloud Storage bucket that triggers the function.

Object Finalize: triggering the function

To trigger the function:

  1. Create an empty gcf-test.txt file in the directory where the sample code is located.

  2. Upload the file to Cloud Storage in order to trigger the function:

    gcloud  
    storage  
    cp  
    gcf-test.txt  
    gs:// YOUR_TRIGGER_BUCKET_NAME 
    

    where YOUR_TRIGGER_BUCKET_NAME is the name of your Cloud Storage bucket where you will upload a test file.

  3. Check the logs to make sure the executions have completed:

     gcloud functions logs read --limit 50 
    

Object Delete

Object delete events are triggered when an object is soft deleted . This happens when an object is overwritten or deleted in a bucket without Object Versioning enabled. Deleting an object by specifying its generation number also results in the object being soft deleted.

Object Delete: deploying the function

Using the same sample code as in the finalize example, deploy the function with object delete as the trigger event. Run the following command in the directory where the sample code is located:

Node.js

gcloud functions deploy helloGCS \
--runtime nodejs20 \
--trigger-resource YOUR_TRIGGER_BUCKET_NAME \
--trigger-event google.storage.object.delete

Use the --runtime flag to specify the runtime ID of a supported Node.js version to run your function.

Python

gcloud functions deploy hello_gcs \
--runtime python312 \
--trigger-resource YOUR_TRIGGER_BUCKET_NAME \
--trigger-event google.storage.object.delete

Use the --runtime flag to specify the runtime ID of a supported Python version to run your function.

Go

gcloud functions deploy HelloGCS \
--runtime go121 \
--trigger-resource YOUR_TRIGGER_BUCKET_NAME \
--trigger-event google.storage.object.delete

Use the --runtime flag to specify the runtime ID of a supported Go version to run your function.

Java

gcloud functions deploy java-gcs-function \
--entry-point functions.HelloGcs \
--runtime java17 \
--memory 512MB \
--trigger-resource YOUR_TRIGGER_BUCKET_NAME \
--trigger-event google.storage.object.delete

Use the --runtime flag to specify the runtime ID of a supported Java version to run your function.

Ruby

gcloud  
functions  
deploy  
hello_gcs  
--runtime  
ruby33  
 \
-
-trigger-resource YOUR_TRIGGER_BUCKET_NAME \
-
-trigger-event google.storage.object.delete

Use the --runtime flag to specify the runtime ID of a supported Ruby version to run your function.

where YOUR_TRIGGER_BUCKET_NAME is the name of the Cloud Storage bucket that triggers the function.

Object Delete: triggering the function

To trigger the function:

  1. Create an empty gcf-test.txt file in the directory where the sample code is located.

  2. Make sure that your bucket is non-versioning:

    gcloud  
    storage  
    buckets  
    update  
    gs:// YOUR_TRIGGER_BUCKET_NAME 
      
    --no-versioning
  3. Upload the file to Cloud Storage:

    gcloud  
    storage  
    cp  
    gcf-test.txt  
    gs:// YOUR_TRIGGER_BUCKET_NAME 
    

    where YOUR_TRIGGER_BUCKET_NAME is the name of your Cloud Storage bucket where you will upload a test file. At this point the function should not execute yet.

  4. Delete the file to trigger the function:

    gcloud  
    storage  
    rm  
    gs:// YOUR_TRIGGER_BUCKET_NAME 
    /gcf-test.txt
  5. Check the logs to make sure the executions have completed:

     gcloud functions logs read --limit 50 
    

Note that the function may take some time to finish executing.

Object Archive

Object archive events are triggered when a live version of an object becomes a noncurrent version. This happens when an object is overwritten or deleted in a bucket with Object Versioning enabled.

Object Archive: deploying the function

Using the same sample code as in the finalize example, deploy the function with object archive as the trigger event. Run the following command in the directory where the sample code is located:

Node.js

gcloud functions deploy helloGCS \
--runtime nodejs20 \
--trigger-resource YOUR_TRIGGER_BUCKET_NAME \
--trigger-event google.storage.object.archive

Use the --runtime flag to specify the runtime ID of a supported Node.js version to run your function.

Python

gcloud functions deploy hello_gcs \
--runtime python312 \
--trigger-resource YOUR_TRIGGER_BUCKET_NAME \
--trigger-event google.storage.object.archive

Use the --runtime flag to specify the runtime ID of a supported Python version to run your function.

Go

gcloud functions deploy HelloGCS \
--runtime go121 \
--trigger-resource YOUR_TRIGGER_BUCKET_NAME \
--trigger-event google.storage.object.archive

Use the --runtime flag to specify the runtime ID of a supported Go version to run your function.

Java

gcloud functions deploy java-gcs-function \
--entry-point functions.HelloGcs \
--runtime java17 \
--memory 512MB \
--trigger-resource YOUR_TRIGGER_BUCKET_NAME \
--trigger-event google.storage.object.archive

Use the --runtime flag to specify the runtime ID of a supported Java version to run your function.

Ruby

gcloud  
functions  
deploy  
hello_gcs  
--runtime  
ruby33  
 \
-
-trigger-resource YOUR_TRIGGER_BUCKET_NAME \
-
-trigger-event google.storage.object.archive

Use the --runtime flag to specify the runtime ID of a supported Ruby version to run your function.

where YOUR_TRIGGER_BUCKET_NAME is the name of the Cloud Storage bucket that triggers the function.

Object Archive: triggering the function

To trigger the function:

  1. Create an empty gcf-test.txt file in the directory where the sample code is located.

  2. Make sure that your bucket has versioning enabled:

    gcloud  
    storage  
    buckets  
    update  
    gs:// YOUR_TRIGGER_BUCKET_NAME 
      
    --versioning
  3. Upload the file to Cloud Storage:

    gcloud  
    storage  
    cp  
    gcf-test.txt  
    gs:// YOUR_TRIGGER_BUCKET_NAME 
    

    where YOUR_TRIGGER_BUCKET_NAME is the name of your Cloud Storage bucket where you will upload a test file. At this point the function should not execute yet.

  4. Archive the file to trigger the function:

    gcloud  
    storage  
    rm  
    gs:// YOUR_TRIGGER_BUCKET_NAME 
    /gcf-test.txt
  5. Watch the logs to make sure the executions have completed:

     gcloud functions logs read --limit 50 
    

Metadata update events are triggered when the metadata of existing object is updated.

Using the same sample code as in the finalize example, deploy the function with metadata update as the trigger event. Run the following command in the directory where the sample code is located:

Node.js

gcloud functions deploy helloGCS \
--runtime nodejs20 \
--trigger-resource YOUR_TRIGGER_BUCKET_NAME \
--trigger-event google.storage.object.metadataUpdate

Use the --runtime flag to specify the runtime ID of a supported Node.js version to run your function.

Python

gcloud functions deploy hello_gcs \
--runtime python312 \
--trigger-resource YOUR_TRIGGER_BUCKET_NAME \
--trigger-event google.storage.object.metadataUpdate

Use the --runtime flag to specify the runtime ID of a supported Python version to run your function.

Go

gcloud functions deploy HelloGCS \
--runtime go121 \
--trigger-resource YOUR_TRIGGER_BUCKET_NAME \
--trigger-event google.storage.object.metadataUpdate

Use the --runtime flag to specify the runtime ID of a supported Go version to run your function.

Java

gcloud functions deploy java-gcs-function \
--entry-point functions.HelloGcs \
--runtime java17 \
--memory 512MB \
--trigger-resource YOUR_TRIGGER_BUCKET_NAME \
--trigger-event google.storage.object.metadataUpdate

Use the --runtime flag to specify the runtime ID of a supported Java version to run your function.

Ruby

gcloud  
functions  
deploy  
hello_gcs  
--runtime  
ruby33  
 \
-
-trigger-resource YOUR_TRIGGER_BUCKET_NAME \
-
-trigger-event google.storage.object.metadataUpdate

Use the --runtime flag to specify the runtime ID of a supported Ruby version to run your function.

where YOUR_TRIGGER_BUCKET_NAME is the name of the Cloud Storage bucket that triggers the function.

To trigger the function:

  1. Create an empty gcf-test.txt file in the directory where the sample code is located.

  2. Make sure that your bucket is non-versioning:

    gcloud  
    storage  
    buckets  
    update  
    gs:// YOUR_TRIGGER_BUCKET_NAME 
      
    --no-versioning
  3. Upload the file to Cloud Storage:

    gcloud  
    storage  
    cp  
    gcf-test.txt  
    gs:// YOUR_TRIGGER_BUCKET_NAME 
    

    where YOUR_TRIGGER_BUCKET_NAME is the name of your Cloud Storage bucket where you will upload a test file. At this point the function should not execute yet.

  4. Update the metadata of the file:

    gcloud  
    storage  
    objects  
    update  
    gs:// YOUR_TRIGGER_BUCKET_NAME 
    /gcf-test.txt  
    --content-type = 
    text/plain
  5. Watch the logs to make sure the executions have completed:

     gcloud functions logs read --limit 50 
    

Clean up

To avoid incurring charges to your Google Cloud account for the resources used in this tutorial, either delete the project that contains the resources, or keep the project and delete the individual resources.

Deleting the project

The easiest way to eliminate billing is to delete the project that you created for the tutorial.

To delete the project:

  1. In the Google Cloud console, go to the Manage resources page.

    Go to Manage resources

  2. In the project list, select the project that you want to delete, and then click Delete .
  3. In the dialog, type the project ID, and then click Shut down to delete the project.

Deleting the function

Deleting Cloud Run functions does not remove any resources stored in Cloud Storage.

To delete the function you created in this tutorial, run the following command:

Node.js

gcloud functions delete helloGCS

Python

gcloud functions delete hello_gcs

Go

gcloud functions delete HelloGCS

Java

gcloud functions delete java-gcs-function

Ruby

gcloud functions delete hello_gcs

You can also delete Cloud Run functions from the Google Cloud console .

What's next

Design a Mobile Site
View Site in Mobile | Classic
Share by: