执行GCloud函数部署及Web UI配置GCS Bucket触发器均失败求助

I’ve run into identical GCS trigger setup issues with Cloud Functions before, and since this works in your other projects, the problem is almost certainly tied to misconfigurations specific to your current project. Let’s walk through the most effective fixes:

• Verify permissions for the GCS trigger service account
  Cloud Functions uses a dedicated service account (service-PROJECT_NUMBER@gcf-admin-robot.iam.gserviceaccount.com) to set up GCS triggers. This account needs specific permissions to create the underlying Pub/Sub topic and link it to your bucket:

  • At the project level: pubsub.topics.create and pubsub.topics.setIamPolicy
  • On the 18_bucket storage bucket: storage.buckets.update (to add the bucket notification) plus storage.objects.get and storage.objects.list (to access trigger objects)
    You can assign these via the IAM console by adding the Cloud Functions Developer role to this service account at the project level, and the Storage Object Viewer role directly on the bucket.

• Check for conflicting bucket notifications
  Stale or misconfigured existing notifications on your bucket can block new trigger setup. Run this command to list active notifications:

  gsutil notification list gs://18_bucket
  

  If you see any notifications linked to deleted functions or orphaned Pub/Sub topics, delete them with:

  gsutil notification delete NOTIFICATION_ID gs://18_bucket
  

  Then try deploying your function again.

• Confirm required APIs are enabled
  GCS triggers depend on three core APIs—make sure all are turned on in your current project:

  • Cloud Functions API
  • Cloud Storage API
  • Cloud Pub/Sub API
    Verify enabled APIs with this command:

  gcloud services list --enabled | grep -E "cloudfunctions|storage|pubsub"
  

  Enable any missing APIs using:

  gcloud services enable cloudfunctions.googleapis.com storage.googleapis.com pubsub.googleapis.com
  

• Check organization policy restrictions
  If your project belongs to an organization, there may be policies blocking bucket notifications or Cloud Function triggers. Head to the IAM & Admin > Organization Policies section in the console and check:

  • constraints/storage.bucketNotifications: Ensure this isn’t set to "Deny"
  • constraints/cloudfunctions.triggersAllowed: Confirm GCS triggers are permitted

• Fallback to manual trigger setup
  If automated setup keeps failing, manually create the Pub/Sub topic and bucket notification first:

  1. Create a dedicated Pub/Sub topic:

     gcloud pubsub topics create gcs-18-bucket-trigger
     

  2. Link your bucket to this topic for OBJECT_FINALIZE events:

     gsutil notification create -t gcs-18-bucket-trigger -e OBJECT_FINALIZE gs://18_bucket
     

  3. Deploy your function to subscribe to this pre-configured topic:

     gcloud beta functions deploy YOUR_FUNCTION_NAME --trigger-topic gcs-18-bucket-trigger
     

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