mirror of
https://github.com/imjasonh/gcloud-help
synced 2026-07-16 20:36:39 +00:00
gcloud: Thu Jan 19 00:56:33 UTC 2023
This commit is contained in:
parent
348d9760ee
commit
1248f773ec
1462 changed files with 51835 additions and 5402 deletions
|
|
@ -2,8 +2,8 @@ NAME
|
|||
gcloud alpha services api-keys create - create an API key
|
||||
|
||||
SYNOPSIS
|
||||
gcloud alpha services api-keys create [--async]
|
||||
[--display-name=DISPLAY_NAME]
|
||||
gcloud alpha services api-keys create [--annotations=[KEY=VALUE,...]]
|
||||
[--async] [--display-name=DISPLAY_NAME]
|
||||
[--api-target=service=SERVICE,[...]
|
||||
--allowed-application=[sha1_fingerprint=SHA1_FINGERPRINT,
|
||||
package_name=PACKAGE_NAME,...]
|
||||
|
|
@ -20,6 +20,10 @@ EXAMPLES
|
|||
$ gcloud alpha services api-keys create --display-name="test name" \
|
||||
--allowed-ips=2620:15c:2c4:203:2776:1f90:6b3b:217,104.133.8.78
|
||||
|
||||
To create a key with annotations:
|
||||
|
||||
$ gcloud alpha services api-keys create --annotations=foo=bar,abc=def
|
||||
|
||||
To create a key with allowed referrers restriction:
|
||||
|
||||
$ gcloud alpha services api-keys create \
|
||||
|
|
@ -61,6 +65,10 @@ EXAMPLES
|
|||
- "barmethod"
|
||||
|
||||
FLAGS
|
||||
--annotations=[KEY=VALUE,...]
|
||||
Annotations are key resource. Specify annotations as a key-value
|
||||
dictionary for small amounts of arbitrary client data.
|
||||
|
||||
--async
|
||||
Return immediately, without waiting for the operation in progress to
|
||||
complete.
|
||||
|
|
@ -69,17 +77,17 @@ FLAGS
|
|||
Display name of the key to create.
|
||||
|
||||
--api-target=service=SERVICE,[...]
|
||||
This flag is repeatable to specify multiple api targets. service and
|
||||
optionally one or multiple specific methods. Both fields are case
|
||||
insensitive. If you need to specify methods, it should be specified
|
||||
with the --flags-file. See $ gcloud topic flags-file for details. See
|
||||
the examples section for how to use --api-target in --flags-file.
|
||||
Repeatable. Specify service and optionally one or multiple specific
|
||||
methods. Both fields are case insensitive. If you need to specify
|
||||
methods, it should be specified with the --flags-file. See $ gcloud
|
||||
topic flags-file for details. See the examples section for how to use
|
||||
--api-target in --flags-file.
|
||||
|
||||
At most one of these can be specified:
|
||||
|
||||
--allowed-application=[sha1_fingerprint=SHA1_FINGERPRINT,package_name=PACKAGE_NAME,...]
|
||||
This flag is repeatable to specify multiple allowed applications. The
|
||||
accepted keys are sha1_fingerprint and package_name.
|
||||
Repeatable. Specify multiple allowed applications. The accepted keys
|
||||
are sha1_fingerprint and package_name.
|
||||
|
||||
--allowed-bundle-ids=[ALLOWED_BUNDLE_IDS,...]
|
||||
iOS app's bundle ids that are allowed to use the key.
|
||||
|
|
@ -104,5 +112,7 @@ 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.
|
||||
access allowlist. This variant is also available:
|
||||
|
||||
$ gcloud beta services api-keys create
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue