Cloud Renames Contribute
RenamedCompute, Security & InfraGoogle Cloud

Cloud Functions (1st gen & 2nd gen) Cloud Run functions

Legacy names Cloud Functions (1st gen & 2nd gen), Cloud Functions

Event-driven serverless functions running on the Cloud Run runtime.

Naming timeline

  1. Cloud Functions (1st gen & 2nd gen)

    · Google Cloud Next '17

    Event-driven serverless functions (public beta launched March 9, 2017; 1st gen GA in July 2018; 2nd gen built on Cloud Run and Eventarc launched in 2022).

  2. Cloud Run functionsCurrent name

    Unified under Cloud Run as Cloud Run functions (lowercase 'f' in 'functions') per the August 21, 2024 release note and August 22, 2024 announcement blog.

What is Cloud Functions (1st gen & 2nd gen) called now?

Cloud Functions (1st gen & 2nd gen) is now called Cloud Run functions, with the latest change on 21 August 2024. Earlier names covered by this entry also include Cloud Functions. Event-driven serverless functions running on the Cloud Run runtime. Only the customer-facing name changed; the underlying technical identifiers remain backward compatible.

Technical identifiers

Technical identifiers unchanged. Only the customer-facing product name changed; the APIs, CLI commands, IAM roles and Terraform resources below keep their legacy identifiers for backward compatibility.

REST / gRPC APIscloudfunctions.googleapis.com run.googleapis.com
gcloud / CLI Commandsgcloud functions gcloud run
IAM Predefined Rolesroles/cloudfunctions.* roles/run.*
Terraform Resourcesgoogle_cloudfunctions_function google_cloudfunctions2_function google_cloud_run_v2_service

Trigger URLs continue using .cloudfunctions.net alongside Cloud Run URLs, and existing cloudfunctions.googleapis.com APIs, gcloud functions commands, and Gen 1/Gen 2 Terraform resources remain supported.

Notes & disambiguation

  • Note lowercase 'f' in 'Cloud Run functions'.
  • Cloud Functions (2nd gen) functions automatically convert into Cloud Run functions and can be detached from cloudfunctions.googleapis.com to be managed exclusively through run.googleapis.com while retaining their .cloudfunctions.net URLs and triggers.
  • Still called Cloud Functions when referencing the legacy v1/v2 APIs (cloudfunctions.googleapis.com), gcloud functions CLI, IAM roles (roles/cloudfunctions.*), Terraform resources (google_cloudfunctions_function, google_cloudfunctions2_function), or .cloudfunctions.net URLs.

Sources & official documentation

Catalog last updated . Spotted an error? Suggest an edit