mirror of
https://github.com/imjasonh/gcloud-help
synced 2026-07-18 14:56:05 +00:00
gcloud: Wed Oct 11 10:37:28 UTC 2023
This commit is contained in:
parent
9641ff6585
commit
c30bb7b4ce
137 changed files with 3139 additions and 267 deletions
|
|
@ -7,7 +7,8 @@ SYNOPSIS
|
|||
--location=LOCATION --requested-link-count=REQUESTED_LINK_COUNT
|
||||
[--admin-enabled] [--customer-name=CUSTOMER_NAME]
|
||||
[--description=DESCRIPTION] [--noc-contact-email=NOC_CONTACT_EMAIL]
|
||||
[--remote-location=REMOTE_LOCATION] [GCLOUD_WIDE_FLAG ...]
|
||||
[--remote-location=REMOTE_LOCATION]
|
||||
[--requested-features=[FEATURES,...]] [GCLOUD_WIDE_FLAG ...]
|
||||
|
||||
DESCRIPTION
|
||||
gcloud compute interconnects create is used to create interconnects. An
|
||||
|
|
@ -92,6 +93,17 @@ OPTIONAL FLAGS
|
|||
remote-locations list command to find the appropriate remote location
|
||||
to use when creating a Cross-Cloud Interconnect.
|
||||
|
||||
--requested-features=[FEATURES,...]
|
||||
List of features requested for this interconnect. FEATURES must be
|
||||
(only one value is supported):
|
||||
|
||||
MACSEC
|
||||
If specified then the interconnect is created on MACsec capable
|
||||
hardware ports. If not specified, the interconnect is created on
|
||||
non-MACsec capable ports first, if available. This parameter can
|
||||
only be provided during interconnect INSERT and cannot be changed
|
||||
using interconnect PATCH.
|
||||
|
||||
GCLOUD WIDE FLAGS
|
||||
These flags are available to all commands: --access-token-file, --account,
|
||||
--billing-project, --configuration, --flags-file, --flatten, --format,
|
||||
|
|
|
|||
|
|
@ -29,6 +29,9 @@ GROUPS
|
|||
locations
|
||||
Read and manipulate Compute Engine interconnect locations.
|
||||
|
||||
macsec
|
||||
Read and manipulate Compute Engine interconnect MACsec configuration.
|
||||
|
||||
remote-locations
|
||||
Read and manipulate Google Compute Engine interconnect remote
|
||||
locations.
|
||||
|
|
|
|||
53
gcloud/compute/interconnects/macsec/add-key
Normal file
53
gcloud/compute/interconnects/macsec/add-key
Normal file
|
|
@ -0,0 +1,53 @@
|
|||
NAME
|
||||
gcloud compute interconnects macsec add-key - add pre-shared key to a
|
||||
Compute Engine interconnect MACsec configuration
|
||||
|
||||
SYNOPSIS
|
||||
gcloud compute interconnects macsec add-key NAME --key-name=KEY_NAME
|
||||
[--start-time=START_TIME] [GCLOUD_WIDE_FLAG ...]
|
||||
|
||||
DESCRIPTION
|
||||
gcloud compute interconnects macsec add-key is used to add a pre-shared key
|
||||
to MACsec configuration of interconnect.
|
||||
|
||||
For an example, refer to the EXAMPLES section below.
|
||||
|
||||
EXAMPLES
|
||||
To add a pre-shared key to MACsec configuration, run:
|
||||
|
||||
$ gcloud compute interconnects macsec add-key example-interconnect \
|
||||
--key-name=default-key --start-time=2021-02-01T12:12:12Z
|
||||
|
||||
POSITIONAL ARGUMENTS
|
||||
NAME
|
||||
Name of the interconnect to update.
|
||||
|
||||
REQUIRED FLAGS
|
||||
--key-name=KEY_NAME
|
||||
A name of pre-shared key being added to MACsec configuration of the
|
||||
interconnect. The name must be 1-63 characters long, and comply with
|
||||
RFC1035.
|
||||
|
||||
OPTIONAL FLAGS
|
||||
--start-time=START_TIME
|
||||
A RFC3339 timestamp on or after which the key is valid. startTime can
|
||||
be in the future. If the keychain has a single key, --start-time can be
|
||||
omitted. If the keychain has multiple keys, --start-time is mandatory
|
||||
for each key. The start times of two consecutive keys must be at least
|
||||
6 hours apart.
|
||||
|
||||
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
|
||||
These variants are also available:
|
||||
|
||||
$ gcloud alpha compute interconnects macsec add-key
|
||||
|
||||
$ gcloud beta compute interconnects macsec add-key
|
||||
|
||||
39
gcloud/compute/interconnects/macsec/get-config
Normal file
39
gcloud/compute/interconnects/macsec/get-config
Normal file
|
|
@ -0,0 +1,39 @@
|
|||
NAME
|
||||
gcloud compute interconnects macsec get-config - get MACsec configuration
|
||||
of a Compute Engine interconnect
|
||||
|
||||
SYNOPSIS
|
||||
gcloud compute interconnects macsec get-config NAME [GCLOUD_WIDE_FLAG ...]
|
||||
|
||||
DESCRIPTION
|
||||
gcloud compute interconnects macsec get-config displays all MACsec
|
||||
configuration data associated with Compute Engine interconnect in a
|
||||
project.
|
||||
|
||||
For an example, refer to the EXAMPLES section below.
|
||||
|
||||
EXAMPLES
|
||||
To displays all MACsec configuration data associated with Compute Engine
|
||||
interconnect in a project, run:
|
||||
|
||||
$ gcloud compute interconnects macsec get-config example-interconnect
|
||||
|
||||
POSITIONAL ARGUMENTS
|
||||
NAME
|
||||
Name of the interconnect to describe.
|
||||
|
||||
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
|
||||
These variants are also available:
|
||||
|
||||
$ gcloud alpha compute interconnects macsec get-config
|
||||
|
||||
$ gcloud beta compute interconnects macsec get-config
|
||||
|
||||
43
gcloud/compute/interconnects/macsec/help
Normal file
43
gcloud/compute/interconnects/macsec/help
Normal file
|
|
@ -0,0 +1,43 @@
|
|||
NAME
|
||||
gcloud compute interconnects macsec - read and manipulate Compute Engine
|
||||
interconnect MACsec configuration
|
||||
|
||||
SYNOPSIS
|
||||
gcloud compute interconnects macsec COMMAND [GCLOUD_WIDE_FLAG ...]
|
||||
|
||||
DESCRIPTION
|
||||
Read and manipulate Compute Engine interconnect MACsec configuration.
|
||||
|
||||
GCLOUD WIDE FLAGS
|
||||
These flags are available to all commands: --help.
|
||||
|
||||
Run $ gcloud help for details.
|
||||
|
||||
COMMANDS
|
||||
COMMAND is one of the following:
|
||||
|
||||
add-key
|
||||
Add pre-shared key to a Compute Engine interconnect MACsec
|
||||
configuration.
|
||||
|
||||
get-config
|
||||
Get MACsec configuration of a Compute Engine interconnect.
|
||||
|
||||
remove-key
|
||||
Remove pre-shared key from a Compute Engine interconnect MACsec
|
||||
configuration.
|
||||
|
||||
update
|
||||
Update a Compute Engine interconnect MACsec configuration.
|
||||
|
||||
update-key
|
||||
Update pre-shared key in a Compute Engine interconnect MACsec
|
||||
configuration.
|
||||
|
||||
NOTES
|
||||
These variants are also available:
|
||||
|
||||
$ gcloud alpha compute interconnects macsec
|
||||
|
||||
$ gcloud beta compute interconnects macsec
|
||||
|
||||
44
gcloud/compute/interconnects/macsec/remove-key
Normal file
44
gcloud/compute/interconnects/macsec/remove-key
Normal file
|
|
@ -0,0 +1,44 @@
|
|||
NAME
|
||||
gcloud compute interconnects macsec remove-key - remove pre-shared key from
|
||||
a Compute Engine interconnect MACsec configuration
|
||||
|
||||
SYNOPSIS
|
||||
gcloud compute interconnects macsec remove-key NAME --key-name=KEY_NAME
|
||||
[GCLOUD_WIDE_FLAG ...]
|
||||
|
||||
DESCRIPTION
|
||||
gcloud compute interconnects macsec remove-key is used to remove pre-shared
|
||||
key from MACsec configuration of interconnect.
|
||||
|
||||
For an example, refer to the EXAMPLES section below.
|
||||
|
||||
EXAMPLES
|
||||
To remove a pre-shared key from MACsec configuration, run:
|
||||
|
||||
$ gcloud compute interconnects macsec remove-key \
|
||||
example-interconnect --key-name=default-key
|
||||
|
||||
POSITIONAL ARGUMENTS
|
||||
NAME
|
||||
Name of the interconnect to update.
|
||||
|
||||
REQUIRED FLAGS
|
||||
--key-name=KEY_NAME
|
||||
The name of pre-shared key being removed from MACsec configuration of
|
||||
the interconnect.
|
||||
|
||||
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
|
||||
These variants are also available:
|
||||
|
||||
$ gcloud alpha compute interconnects macsec remove-key
|
||||
|
||||
$ gcloud beta compute interconnects macsec remove-key
|
||||
|
||||
54
gcloud/compute/interconnects/macsec/update
Normal file
54
gcloud/compute/interconnects/macsec/update
Normal file
|
|
@ -0,0 +1,54 @@
|
|||
NAME
|
||||
gcloud compute interconnects macsec update - update a Compute Engine
|
||||
interconnect MACsec configuration
|
||||
|
||||
SYNOPSIS
|
||||
gcloud compute interconnects macsec update NAME [--enabled] [--fail-open]
|
||||
[GCLOUD_WIDE_FLAG ...]
|
||||
|
||||
DESCRIPTION
|
||||
gcloud compute interconnects macsec update is used to update MACsec
|
||||
configuration of interconnect. An interconnect represents a single specific
|
||||
connection between Google and the customer.
|
||||
|
||||
For an example, refer to the EXAMPLES section below.
|
||||
|
||||
EXAMPLES
|
||||
To enable MACsec on an interconnect, run:
|
||||
|
||||
$ gcloud compute interconnects macsec update example-interconnect \
|
||||
--enabled
|
||||
|
||||
POSITIONAL ARGUMENTS
|
||||
NAME
|
||||
Name of the interconnect to update.
|
||||
|
||||
FLAGS
|
||||
--enabled
|
||||
Enable or disable MACsec on this Interconnect. MACsec enablement will
|
||||
fail if the MACsec configuration is not specified. Use --no-enabled to
|
||||
disable it.
|
||||
|
||||
--fail-open
|
||||
If enabled, the Interconnect will be configured with a should-secure
|
||||
MACsec security policy, that allows the Google router to fallback to
|
||||
cleartext traffic if the MKA session cannot be established. By default,
|
||||
the Interconnect will be configured with a must-secure security policy
|
||||
that drops all traffic if the MKA session cannot be established with
|
||||
your router. Use --no-fail-open to disable it.
|
||||
|
||||
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
|
||||
These variants are also available:
|
||||
|
||||
$ gcloud alpha compute interconnects macsec update
|
||||
|
||||
$ gcloud beta compute interconnects macsec update
|
||||
|
||||
54
gcloud/compute/interconnects/macsec/update-key
Normal file
54
gcloud/compute/interconnects/macsec/update-key
Normal file
|
|
@ -0,0 +1,54 @@
|
|||
NAME
|
||||
gcloud compute interconnects macsec update-key - update pre-shared key in a
|
||||
Compute Engine interconnect MACsec configuration
|
||||
|
||||
SYNOPSIS
|
||||
gcloud compute interconnects macsec update-key NAME --key-name=KEY_NAME
|
||||
[--start-time=START_TIME] [GCLOUD_WIDE_FLAG ...]
|
||||
|
||||
DESCRIPTION
|
||||
gcloud compute interconnects macsec update-key is used to update a
|
||||
pre-shared key in MACsec configuration of interconnect.
|
||||
|
||||
For an example, refer to the EXAMPLES section below.
|
||||
|
||||
EXAMPLES
|
||||
To update a pre-shared key in MACsec configuration, run:
|
||||
|
||||
$ gcloud compute interconnects macsec update-key \
|
||||
example-interconnect --key-name=default-key \
|
||||
--start-time=2021-02-01T12:12:12Z
|
||||
|
||||
POSITIONAL ARGUMENTS
|
||||
NAME
|
||||
Name of the interconnect to update.
|
||||
|
||||
REQUIRED FLAGS
|
||||
--key-name=KEY_NAME
|
||||
A name of pre-shared key being added to MACsec configuration of the
|
||||
interconnect. The name must be 1-63 characters long, and comply with
|
||||
RFC1035.
|
||||
|
||||
OPTIONAL FLAGS
|
||||
--start-time=START_TIME
|
||||
A RFC3339 timestamp on or after which the key is valid. startTime can
|
||||
be in the future. If the keychain has a single key, --start-time can be
|
||||
omitted. If the keychain has multiple keys, --start-time is mandatory
|
||||
for each key. The start times of two consecutive keys must be at least
|
||||
6 hours apart.
|
||||
|
||||
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
|
||||
These variants are also available:
|
||||
|
||||
$ gcloud alpha compute interconnects macsec update-key
|
||||
|
||||
$ gcloud beta compute interconnects macsec update-key
|
||||
|
||||
Loading…
Add table
Add a link
Reference in a new issue