gcloud beta functions upgrade

NAME
gcloud beta functions upgrade - upgrade a 1st gen Cloud Function to the Cloud Run function
SYNOPSIS
gcloud beta functions upgrade(NAME :--region=REGION)[--abort    |--commit    |--redirect-traffic    |--rollback-traffic    |--setup-config--trigger-service-account=TRIGGER_SERVICE_ACCOUNT][GCLOUD_WIDE_FLAG]
DESCRIPTION
(BETA) Upgrade a 1st gen Cloud Function to the Cloud Run function.
EXAMPLES
To start the upgrade process for a 1st gen functionfoo and createa Cloud Run function copy, run:
gcloudbetafunctionsupgradefoo--setup-config

Once you are ready to redirect traffic to the Cloud Run function copy, run:

gcloudbetafunctionsupgradefoo--redirect-traffic

If you find you need to do more local testing you can rollback traffic to the1st gen copy:

gcloudbetafunctionsupgradefoo--rollback-traffic

Once you're ready to finish upgrading and delete the 1st gen copy, run:

gcloudbetafunctionsupgradefoo--commit

You can abort the upgrade process at any time by running:

gcloudbetafunctionsupgradefoo--abort
POSITIONAL ARGUMENTS
Function resource - The Cloud Function name to upgrade. The arguments in thisgroup can be used to specify the attributes of this resource. (NOTE) Someattributes are not given arguments in this group but can be set in other ways.

To set theproject attribute:

  • provide the argumentNAME on the command line with a fullyspecified name;
  • provide the argument--project on the command line;
  • set the propertycore/project.

This must be specified.

NAME
ID of the function or fully qualified identifier for the function.

To set thefunction attribute:

  • provide the argumentNAME on the command line.

This positional argument must be specified if any of the other arguments in thisgroup are specified.

--region=REGION
The Cloud region for the function. Overrides the defaultfunctions/region property value for this command invocation.

To set theregion attribute:

  • provide the argumentNAME on the command line with a fullyspecified name;
  • provide the argument--region on the command line;
  • set the propertyfunctions/region.
FLAGS
Upgrade a 1st gen Cloud Function to the 2nd gen environment. You must specifyone of the following flags:
  • --setup-config and optionally--trigger-service-account,
  • --redirect-traffic,
  • --rollback-traffic,
  • --commit,
  • --abort.
At most one of these can be specified:
--abort
Undoes all steps of the upgrade process done so far. All traffic will point tothe original 1st gen function copy and the 2nd gen function copy will bedeleted.
--commit
Finishes the upgrade process and permanently deletes the original 1st gen copyof the function.
--redirect-traffic
Redirects production traffic to the 2nd gen copy of the function.
--rollback-traffic
Rolls back production traffic to the original 1st gen copy of the function. The2nd gen copy will still be available for testing.
--setup-config
Sets up the function upgrade config by creating a 2nd gen copy of the function'scode and configuration.
--trigger-service-account=TRIGGER_SERVICE_ACCOUNT
The email address of the IAM service account associated with the Eventarctrigger for the function. This is used for authenticated invocation.

If not provided, the function will use the project's default service account forCompute Engine.

GCLOUD WIDE FLAGS
These flags are available to all commands:--access-token-file,--account,--billing-project,--configuration,--flags-file,--flatten,--format,--help,--impersonate-service-account,--log-http,--project,--quiet,--trace-token,--user-output-enabled,--verbosity.

Run$gcloud help for details.

NOTES
This command is currently in beta and might change without notice. This variantis also available:
gcloudalphafunctionsupgrade

Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2025-08-19 UTC.