imjasonh/gcloud-help
1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-18 14:56:05 +00:00
Code Activity

gcloud: Thu Jan 23 10:02:29 UTC 2025

Browse source
This commit is contained in:
Automated 2025-01-23 10:02:29 +00:00
parent 4a036681b1
commit 861d4011dc
116 changed files with 1271 additions and 2834 deletions
Download patch file Download diff file Expand all files Collapse all files

3
gcloud/beta/run/help
View file

@ -26,9 +26,6 @@ GROUPS
domain-mappings
(BETA) View and manage your Cloud Run domain mappings.
integrations
(BETA) View and manage your Cloud Run (fully managed) integrations.
jobs
(BETA) View and manage your Cloud Run jobs.

62
gcloud/beta/run/integrations/create
View file

@ -1,62 +0,0 @@
NAME
gcloud beta run integrations create - create a Cloud Run Integration
SYNOPSIS
gcloud beta run integrations create --type=TYPE [--name=NAME]
[--parameters=[PARAMETER=VALUE,...]] [--region=REGION]
[--service=SERVICE] [--service-account=SERVICE_ACCOUNT]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Create a Cloud Run Integration.
EXAMPLES
To create and attach a redis instance to a Cloud Run service
$ gcloud beta run integrations create --type=redis \
--service=myservice
To attach a custom domain to a Cloud Run service
$ gcloud beta run integrations create --type=custom-domains \
--parameters='set-mapping=example.com/*:myservice'
REQUIRED FLAGS
--type=TYPE
Type of the integration. To see available types and usage, use "gcloud
run integrations types list" command.
OPTIONAL FLAGS
--name=NAME
Name of the integration.
--parameters=[PARAMETER=VALUE,...]
Comma-separated list of parameter names and values. Names must be one
of the parameters shown when describing the integration type. Only
simple values can be specified with this flag.
--region=REGION
Region in which the resource can be found. Alternatively, set the
property [run/region].
--service=SERVICE
Name of the Cloud Run service to attach to the integration. It is
required for some integrations.
--service-account=SERVICE_ACCOUNT
Name of the service account to use when deploying the integration.
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
variant is also available:
$ gcloud alpha run integrations create

42
gcloud/beta/run/integrations/delete
View file

@ -1,42 +0,0 @@
NAME
gcloud beta run integrations delete - delete a Cloud Run Integration and
its associated resources
SYNOPSIS
gcloud beta run integrations delete NAME [--region=REGION]
[--service-account=SERVICE_ACCOUNT] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Delete a Cloud Run Integration and its associated resources.
EXAMPLES
To delete a redis integration and the associated resources
$ gcloud beta run integrations delete my-redis-integration
POSITIONAL ARGUMENTS
NAME
Name of the integration.
FLAGS
--region=REGION
Region in which the resource can be found. Alternatively, set the
property [run/region].
--service-account=SERVICE_ACCOUNT
Name of the service account to use when deploying the integration.
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
variant is also available:
$ gcloud alpha run integrations delete

38
gcloud/beta/run/integrations/describe
View file

@ -1,38 +0,0 @@
NAME
gcloud beta run integrations describe - describe a Cloud Run Integration
SYNOPSIS
gcloud beta run integrations describe NAME [--region=REGION]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Describe a Cloud Run Integration.
EXAMPLES
To describe an integration
$ gcloud beta run integrations describe my-redis-integration
POSITIONAL ARGUMENTS
NAME
Name of the integration.
FLAGS
--region=REGION
Region in which the resource can be found. Alternatively, set the
property [run/region].
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
variant is also available:
$ gcloud alpha run integrations describe

57
gcloud/beta/run/integrations/help
View file

@ -1,57 +0,0 @@
NAME
gcloud beta run integrations - view and manage your Cloud Run
(fully managed) integrations
SYNOPSIS
gcloud beta run integrations GROUP | COMMAND [--region=REGION]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) This set of commands can be used to view and manage your Cloud Run
integrations.
EXAMPLES
To list your existing integrations, run:
$ gcloud beta run integrations list
FLAGS
--region=REGION
Region in which the resource can be found. Alternatively, set the
property [run/region].
GCLOUD WIDE FLAGS
These flags are available to all commands: --help.
Run $ gcloud help for details.
GROUPS
GROUP is one of the following:
types
(BETA) View available Cloud Run (fully managed) integrations types.
COMMANDS
COMMAND is one of the following:
create
(BETA) Create a Cloud Run Integration.
delete
(BETA) Delete a Cloud Run Integration and its associated resources.
describe
(BETA) Describe a Cloud Run Integration.
list
(BETA) List Cloud Run Integrations.
update
(BETA) Update a Cloud Run Integration.
NOTES
This command is currently in beta and might change without notice. This
variant is also available:
$ gcloud alpha run integrations

82
gcloud/beta/run/integrations/list
View file

@ -1,82 +0,0 @@
NAME
gcloud beta run integrations list - list Cloud Run Integrations
SYNOPSIS
gcloud beta run integrations list [--region=REGION] [--service=SERVICE]
[--type=TYPE] [--filter=EXPRESSION] [--limit=LIMIT]
[--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) List Cloud Run Integrations.
EXAMPLES
List all Cloud Run Integrations within the current project
$ gcloud beta run integrations list
List all Cloud Run Integrations of a particular type
$ gcloud beta run integrations list --type=redis
List all Cloud Run Integrations attached to a particular Service
$ gcloud beta run integrations list --service=my-service
FLAGS
--region=REGION
Region in which the resource can be found. Alternatively, set the
property [run/region].
--service=SERVICE
Filter Integrations by Name of Cloud Run service.
--type=TYPE
Filter Integrations by Type of Integration.
LIST COMMAND FLAGS
--filter=EXPRESSION
Apply a Boolean filter EXPRESSION to each resource item to be listed.
If the expression evaluates True, then that item is listed. For more
details and examples of filter expressions, run $ gcloud topic filters.
This flag interacts with other flags that are applied in this order:
--flatten, --sort-by, --filter, --limit.
--limit=LIMIT
Maximum number of resources to list. The default is unlimited. This
flag interacts with other flags that are applied in this order:
--flatten, --sort-by, --filter, --limit.
--page-size=PAGE_SIZE
Some services group resource list output into pages. This flag
specifies the maximum number of resources per page. The default is
determined by the service if it supports paging, otherwise it is
unlimited (no paging). Paging may be applied before or after --filter
and --limit depending on the service.
--sort-by=[FIELD,...]
Comma-separated list of resource field key names to sort by. The
default order is ascending. Prefix a field with ``~'' for descending
order on that field. This flag interacts with other flags that are
applied in this order: --flatten, --sort-by, --filter, --limit.
--uri
Print a list of resource URIs instead of the default output, and change
the command output to a list of URIs. If this flag is used with
--format, the formatting is applied on this URI list. To display URIs
alongside other keys instead, use the uri() transform.
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
variant is also available:
$ gcloud alpha run integrations list

39
gcloud/beta/run/integrations/types/describe
View file

@ -1,39 +0,0 @@
NAME
gcloud beta run integrations types describe - describes a Cloud Run
Integration type
SYNOPSIS
gcloud beta run integrations types describe TYPE [--region=REGION]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Describes a Cloud Run Integration type.
EXAMPLES
To describe an integration type
$ gcloud beta run integrations types describe [TYPE]
POSITIONAL ARGUMENTS
TYPE
Type of the integration.
FLAGS
--region=REGION
Region in which the resource can be found. Alternatively, set the
property [run/region].
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
variant is also available:
$ gcloud alpha run integrations types describe

42
gcloud/beta/run/integrations/types/help
View file

@ -1,42 +0,0 @@
NAME
gcloud beta run integrations types - view available Cloud Run
(fully managed) integrations types
SYNOPSIS
gcloud beta run integrations types COMMAND [--region=REGION]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) This set of commands can be used to view Cloud Run integrations
types.
EXAMPLES
To list available integrations types, run:
$ gcloud beta run integrations types list
FLAGS
--region=REGION
Region in which the resource can be found. Alternatively, set the
property [run/region].
GCLOUD WIDE FLAGS
These flags are available to all commands: --help.
Run $ gcloud help for details.
COMMANDS
COMMAND is one of the following:
describe
(BETA) Describes a Cloud Run Integration type.
list
(BETA) Lists Cloud Run Integration Types.
NOTES
This command is currently in beta and might change without notice. This
variant is also available:
$ gcloud alpha run integrations types

67
gcloud/beta/run/integrations/types/list
View file

@ -1,67 +0,0 @@
NAME
gcloud beta run integrations types list - lists Cloud Run Integration Types
SYNOPSIS
gcloud beta run integrations types list [--region=REGION]
[--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE]
[--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Lists Cloud Run Integration Types.
EXAMPLES
To list all integration types
$ gcloud beta run integrations types list
FLAGS
--region=REGION
Region in which the resource can be found. Alternatively, set the
property [run/region].
LIST COMMAND FLAGS
--filter=EXPRESSION
Apply a Boolean filter EXPRESSION to each resource item to be listed.
If the expression evaluates True, then that item is listed. For more
details and examples of filter expressions, run $ gcloud topic filters.
This flag interacts with other flags that are applied in this order:
--flatten, --sort-by, --filter, --limit.
--limit=LIMIT
Maximum number of resources to list. The default is unlimited. This
flag interacts with other flags that are applied in this order:
--flatten, --sort-by, --filter, --limit.
--page-size=PAGE_SIZE
Some services group resource list output into pages. This flag
specifies the maximum number of resources per page. The default is
determined by the service if it supports paging, otherwise it is
unlimited (no paging). Paging may be applied before or after --filter
and --limit depending on the service.
--sort-by=[FIELD,...]
Comma-separated list of resource field key names to sort by. The
default order is ascending. Prefix a field with ``~'' for descending
order on that field. This flag interacts with other flags that are
applied in this order: --flatten, --sort-by, --filter, --limit.
--uri
Print a list of resource URIs instead of the default output, and change
the command output to a list of URIs. If this flag is used with
--format, the formatting is applied on this URI list. To display URIs
alongside other keys instead, use the uri() transform.
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
variant is also available:
$ gcloud alpha run integrations types list

58
gcloud/beta/run/integrations/update
View file

@ -1,58 +0,0 @@
NAME
gcloud beta run integrations update - update a Cloud Run Integration
SYNOPSIS
gcloud beta run integrations update NAME
[--parameters=[PARAMETER=VALUE,...]] [--region=REGION]
[--service-account=SERVICE_ACCOUNT]
[--add-service=ADD_SERVICE | --remove-service=REMOVE_SERVICE]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Update a Cloud Run Integration.
EXAMPLES
To update a redis integration to change the cache size
$ gcloud beta run integrations update redis-integration \
--parameters=memory-size-gb=5
POSITIONAL ARGUMENTS
NAME
Name of the integration.
FLAGS
--parameters=[PARAMETER=VALUE,...]
Comma-separated list of parameter names and values. Names must be one
of the parameters shown when describing the integration type. Only
simple values can be specified with this flag.
--region=REGION
Region in which the resource can be found. Alternatively, set the
property [run/region].
--service-account=SERVICE_ACCOUNT
Name of the service account to use when deploying the integration.
At most one of these can be specified:
--add-service=ADD_SERVICE
Name of the Cloud Run service to attach to the integration.
--remove-service=REMOVE_SERVICE
Name of the Cloud Run service to remove from the integration.
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
variant is also available:
$ gcloud alpha run integrations update