gcloud alpha run integrations create

NAME
gcloud alpha run integrations create - create a Cloud Run Integration
SYNOPSIS
gcloud alpha run integrations create --type=TYPE [--name=NAME] [--parameters=[PARAMETER=VALUE,…]] [--region=REGION] [--service=SERVICE] [--service-account=SERVICE_ACCOUNT] [GCLOUD_WIDE_FLAG …]
DESCRIPTION
(ALPHA) Create a Cloud Run Integration.
EXAMPLES
To create and attach a redis instance to a Cloud Run service 
gcloud alpha run integrations create --type=redis --service=myservice

To attach a custom domain to a Cloud Run service 

gcloud alpha 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 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. This variant is also available: 
gcloud beta run integrations create