Skip to main content

GCP Cloud Functions Function

Google Cloud Functions is Google Cloud Platform’s event-driven, serverless compute offering. A Cloud Function is a single-purpose piece of code that is deployed to Google’s infrastructure and executed automatically in response to HTTP requests or to events from many GCP services (Storage, Pub/Sub, Firestore, etc.). Functions scale up and down on demand, require no server management, and run within a fully managed runtime.
Official documentation: https://cloud.google.com/functions

Supported Methods​

  • GET: Get a gcp-cloud-functions-function by its "locations|functions"
  • LIST
  • SEARCH: Search for gcp-cloud-functions-function by its "locations"

gcp-storage-bucket​

A Cloud Function’s source code can be uploaded from a Cloud Storage bucket, and functions can also be triggered by Cloud Storage object change events or interact with buckets at run-time. Overmind links the function to any bucket it relies on or affects.

gcp-run-service​

2nd-generation Cloud Functions are deployed on top of Cloud Run; each function is materialised as an underlying Cloud Run service. This link highlights that deleting or altering the Cloud Run service will directly impact the function.

gcp-pub-sub-topic​

Functions can be triggered by messages published to a Pub/Sub topic and can themselves publish messages to other topics. The link surfaces the dependency between the function and any topic used for event ingress or egress.

gcp-cloud-kms-crypto-key​

When a function uses secrets or environment variables encrypted with Cloud KMS, it must be granted access to the relevant crypto keys. Overmind records these relationships so key rotation or permission changes can be assessed for risk.

gcp-iam-service-account​

Every Cloud Function runs as an IAM service account that defines its permissions across GCP. The link shows which service account a function uses and, conversely, which functions depend on a given service account, aiding least-privilege reviews and impact analysis.