- NAME
-
- gcloud beta beyondcorp security-gateways applications create - create applications
- SYNOPSIS
-
-
gcloud beta beyondcorp security-gateways applications create
(APPLICATION
:--location
=LOCATION
--security-gateway
=SECURITY_GATEWAY
)--endpoint-matchers
=[hostname
=HOSTNAME
],[ports
=PORTS
] [--async
] [--display-name
=DISPLAY_NAME
] [--request-id
=REQUEST_ID
] [--upstreams
=[egressPolicy
=EGRESSPOLICY
],[network
=NETWORK
]] [GCLOUD_WIDE_FLAG …
]
-
- DESCRIPTION
-
(BETA)
Create an application - EXAMPLES
-
To create the application, run:
gcloud beta beyondcorp security-gateways applications create
- POSITIONAL ARGUMENTS
-
-
Application resource - Identifier. Name of the resource. 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
application
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.
APPLICATION
-
ID of the application or fully qualified identifier for the application.
To set the
application
attribute:-
provide the argument
application
on the command line.
This positional argument must be specified if any of the other arguments in this group are specified.
-
provide the argument
--location
=LOCATION
-
The location id of the application resource. We support only global location.
To set the
location
attribute:-
provide the argument
application
on the command line with a fully specified name; -
provide the argument
--location
on the command line.
-
provide the argument
--security-gateway
=SECURITY_GATEWAY
-
The securityGateway id of the application resource.
To set the
security-gateway
attribute:-
provide the argument
application
on the command line with a fully specified name; -
provide the argument
--security-gateway
on the command line.
-
provide the argument
-
provide the argument
-
Application resource - Identifier. Name of the resource. 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.
- REQUIRED FLAGS
-
--endpoint-matchers
=[hostname
=HOSTNAME
],[ports
=PORTS
]-
Required, Endpoint matchers associated with an application. A combination of
hostname and ports as endpoint matchers is used to match the application. Match
conditions for OR logic. An array of match conditions to allow for multiple
matching criteria. The rule is considered a match if one of the conditions is
met. The conditions can be one of the following combinations (Hostname),
(Hostname & Ports)
EXAMPLES: Hostname - ("
.example.com"), ("xyz.example.com") Hostname and Ports - ("example.com" and "22"), ("example.com" and "22,33") etc.
hostname- Hostname of the application.
- Ports of the application.
--endpoint-matchers=hostname=string,ports=[int] --endpoint-matchers=hostname=string,ports=[int]
--endpoint-matchers='[{"hostname": "string", "ports": [int]}]'
--endpoint-matchers=path_to_file.(yaml|json)
--async
- Return immediately, without waiting for the operation in progress to complete.
--display-name
=DISPLAY_NAME
- An arbitrary user-provided name for the Application resource. Cannot exceed 64 characters.
--request-id
=REQUEST_ID
- An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore request if it has already been completed. The server will guarantee that for at least 60 minutes since the first request.
--upstreams
=[egressPolicy
=EGRESSPOLICY
],[network
=NETWORK
]-
Which upstream resources to forward traffic to.
egressPolicy
-
Routing policy information.
regions
- List of the regions where the application sends traffic.
network
-
Network to forward traffic to.
name
-
Network name is of the format:
projects/{project}/global/networks/{network}.
Shorthand Example:
--upstreams=egressPolicy={regions=[string]},network={name=string} --upstreams=egressPolicy={regions=[string]},network={name=string}
JSON Example:
--upstreams='[{"egressPolicy": {"regions": ["string"]}, "network": {"name": "string"}}]'
File Example:
--upstreams=path_to_file.(yaml|json)
--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.
beyondcorp/v1
API. The full documentation for
this API can be found at: https://cloud.google.com/