imjasonh/gcloud-help
1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-16 12:22:03 +00:00
Code Activity

gcloud: Wed May 15 09:19:06 UTC 2024

Browse source
This commit is contained in:
Automated 2024-05-15 09:19:06 +00:00
parent e8259d86b1
commit 3b84182be4
193 changed files with 10091 additions and 581 deletions
Download patch file Download diff file Expand all files Collapse all files

6
gcloud/alpha/functions/deploy
View file

@ -442,6 +442,12 @@ FLAGS
--clear-max-instances
Clears the maximum instances setting for the function.
If it's any 2nd gen function or a 1st gen HTTP function, this flag
sets maximum instances to 0, which means there is no limit to maximum
instances. If it's an event-driven 1st gen function, this flag sets
maximum instances to 3000, which is the default value for 1st gen
functions.
--max-instances=MAX_INSTANCES
Sets the maximum number of instances for the function. A function
execution that would exceed max-instances times out.

3
gcloud/alpha/functions/help
View file

@ -69,9 +69,6 @@ COMMANDS
set-iam-policy
(ALPHA) Sets IAM policy for a Google Cloud Function.
upgrade
(ALPHA) Upgrade a 1st gen Cloud Function to the 2nd gen environment.
NOTES
This command is currently in alpha and might change without notice. If this
command fails with API permission errors despite specifying the correct

105
gcloud/alpha/functions/upgrade
View file

@ -1,105 +0,0 @@
NAME
gcloud alpha functions upgrade - upgrade a 1st gen Cloud Function to the
2nd gen environment
SYNOPSIS
gcloud alpha functions upgrade (NAME : --region=REGION)
[--abort | --commit | --redirect-traffic | --rollback-traffic
| --setup-config] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(ALPHA) Upgrade a 1st gen Cloud Function to the 2nd gen environment.
EXAMPLES
To start the upgrade process for a 1st gen function foo and create a 2nd
gen copy, run:
$ gcloud alpha functions upgrade foo --setup-config
Once you are ready to redirect traffic to the 2nd gen copy, run:
$ gcloud alpha functions upgrade foo --redirect-traffic
If you find you need to do more local testing you can rollback traffic to
the 1st gen copy:
$ gcloud alpha functions upgrade foo --rollback-traffic
Once you're ready to finish upgrading and delete the 1st gen copy, run:
$ gcloud alpha functions upgrade foo --commit
You can abort the upgrade process at any time by running:
$ gcloud alpha functions upgrade foo --abort
POSITIONAL ARGUMENTS
Function resource - The Cloud function name to upgrade. The arguments in
this group can be used to specify the attributes of this resource. (NOTE)
Some attributes are not given arguments in this group but can be set in
other ways.
To set the project attribute:
◆ provide the argument NAME on the command line with a fully specified
name;
◆ provide the argument --project on the command line;
◆ set the property core/project.
This must be specified.
NAME
ID of the function or fully qualified identifier for the function.
To set the function attribute:
▸ provide the argument NAME on the command line.
This positional argument must be specified if any of the other
arguments in this group are specified.
--region=REGION
The Cloud region for the function. Overrides the default
functions/region property value for this command invocation.
To set the region attribute:
▸ provide the argument NAME on the command line with a fully
specified name;
▸ provide the argument --region on the command line;
▸ set the property functions/region.
FLAGS
At most one of these can be specified:
--abort
Undoes all steps of the upgrade process done so far. All traffic will
point to the original 1st gen function copy and the 2nd gen function
copy will be deleted.
--commit
Finishes the upgrade process and permanently deletes the original 1st
gen copy of 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. The 2nd 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's code and configuration.
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 alpha and might change without notice. If this
command fails with API permission errors despite specifying the correct
project, you might be trying to access an API with an invitation-only early
access allowlist.