mirror of
https://github.com/imjasonh/gcloud-help
synced 2026-07-18 23:08:48 +00:00
gcloud: Thu Sep 8 09:21:50 UTC 2022
This commit is contained in:
parent
6749f65ca2
commit
e7bec9b31b
154 changed files with 2457 additions and 577 deletions
71
gcloud/logging/settings/describe
Normal file
71
gcloud/logging/settings/describe
Normal file
|
|
@ -0,0 +1,71 @@
|
|||
NAME
|
||||
gcloud logging settings describe - displays the settings for the Cloud
|
||||
Logging Logs Router
|
||||
|
||||
SYNOPSIS
|
||||
gcloud logging settings describe
|
||||
[--billing-account=BILLING_ACCOUNT_ID | --folder=FOLDER_ID
|
||||
| --organization=ORGANIZATION_ID | --project=PROJECT_ID]
|
||||
[GCLOUD_WIDE_FLAG ...]
|
||||
|
||||
DESCRIPTION
|
||||
If kmsKeyName is present in the output, then CMEK is enabled for your
|
||||
project, folder, organization or billing-account. You can also find the
|
||||
Logs Router service account using this command.
|
||||
|
||||
EXAMPLES
|
||||
To describe the Logs Router settings for a project, run:
|
||||
|
||||
$ gcloud logging settings describe --project=[PROJECT_ID]
|
||||
|
||||
To describe the Logs Router settings for an organization, run:
|
||||
|
||||
$ gcloud logging settings describe --organization=[ORGANIZATION_ID]
|
||||
|
||||
kmsKeyName:
|
||||
'projects/my-project/locations/my-location/keyRings/my-keyring/cryptoKeys/key'
|
||||
name: 'organizations/[ORGANIZATION_ID]/settings'
|
||||
serviceAccountId:
|
||||
'[SERVICE_ACCOUNT_ID]@gcp-sa-logging.iam.gserviceaccount.com'
|
||||
|
||||
FLAGS
|
||||
At most one of these can be specified:
|
||||
|
||||
--billing-account=BILLING_ACCOUNT_ID
|
||||
Describe settings associated with this billing account.
|
||||
|
||||
--folder=FOLDER_ID
|
||||
Describe settings associated with this folder.
|
||||
|
||||
--organization=ORGANIZATION_ID
|
||||
Describe settings associated with this organization.
|
||||
|
||||
--project=PROJECT_ID
|
||||
Describe settings associated with this project.
|
||||
|
||||
The Google Cloud project ID to use for this invocation. If omitted,
|
||||
then the current project is assumed; the current project can be
|
||||
listed using gcloud config list --format='text(core.project)' and can
|
||||
be set using gcloud config set project PROJECTID.
|
||||
|
||||
--project and its fallback core/project property play two roles in
|
||||
the invocation. It specifies the project of the resource to operate
|
||||
on. It also specifies the project for API enablement check, quota,
|
||||
and billing. To specify a different project for quota and billing,
|
||||
use --billing-project or billing/quota_project property.
|
||||
|
||||
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 logging settings describe
|
||||
|
||||
$ gcloud beta logging settings describe
|
||||
|
||||
31
gcloud/logging/settings/help
Normal file
31
gcloud/logging/settings/help
Normal file
|
|
@ -0,0 +1,31 @@
|
|||
NAME
|
||||
gcloud logging settings - manages the org settings for the Cloud Logging
|
||||
Logs Router
|
||||
|
||||
SYNOPSIS
|
||||
gcloud logging settings COMMAND [GCLOUD_WIDE_FLAG ...]
|
||||
|
||||
DESCRIPTION
|
||||
Manages the org settings for the Cloud Logging Logs Router.
|
||||
|
||||
GCLOUD WIDE FLAGS
|
||||
These flags are available to all commands: --help.
|
||||
|
||||
Run $ gcloud help for details.
|
||||
|
||||
COMMANDS
|
||||
COMMAND is one of the following:
|
||||
|
||||
describe
|
||||
Displays the settings for the Cloud Logging Logs Router.
|
||||
|
||||
update
|
||||
Updates the settings for the Cloud Logging Logs Router.
|
||||
|
||||
NOTES
|
||||
These variants are also available:
|
||||
|
||||
$ gcloud alpha logging settings
|
||||
|
||||
$ gcloud beta logging settings
|
||||
|
||||
133
gcloud/logging/settings/update
Normal file
133
gcloud/logging/settings/update
Normal file
|
|
@ -0,0 +1,133 @@
|
|||
NAME
|
||||
gcloud logging settings update - updates the settings for the Cloud Logging
|
||||
Logs Router
|
||||
|
||||
SYNOPSIS
|
||||
gcloud logging settings update
|
||||
(--folder=FOLDER_ID | --organization=ORGANIZATION_ID)
|
||||
[--disable-default-sink] [--storage-location=STORAGE_LOCATION]
|
||||
[--clear-kms-key | [--kms-key-name=KMS_KEY_NAME
|
||||
: --kms-keyring=KMS_KEYRING
|
||||
--kms-location=KMS_LOCATION --kms-project=KMS_PROJECT]]
|
||||
[GCLOUD_WIDE_FLAG ...]
|
||||
|
||||
DESCRIPTION
|
||||
Use this command to update the --kms-key-name, --storage-location and
|
||||
--disable-default-sink associated with the Cloud Logging Logs Router.
|
||||
|
||||
The Cloud KMS key must already exist and Cloud Logging must have permission
|
||||
to access it.
|
||||
|
||||
The storage location must be allowed by Org Policy.
|
||||
|
||||
Customer-managed encryption keys (CMEK) for the Logs Router can currently
|
||||
only be configured at the organization-level and will apply to all projects
|
||||
in the organization.
|
||||
|
||||
EXAMPLES
|
||||
To enable CMEK for the Logs Router for an organization, run:
|
||||
|
||||
$ gcloud logging settings update --organization=[ORGANIZATION_ID] \
|
||||
--kms-key-name='projects/my-project/locations/my-location/keyRin\
|
||||
gs/my-keyring/cryptoKeys/key'
|
||||
|
||||
To disable CMEK for the Logs Router for an organization, run:
|
||||
|
||||
$ gcloud logging settings update --organization=[ORGANIZATION_ID] \
|
||||
--clear-kms-key
|
||||
|
||||
To update storage location for the Logs Router for an organization, run:
|
||||
|
||||
$ gcloud logging settings update --organization=[ORGANIZATION_ID] \
|
||||
--storage-location=[LOCATION_ID]
|
||||
|
||||
To update storage location for the Logs Router for a folder, run:
|
||||
|
||||
$ gcloud logging settings update --folder=[FOLDER_ID] \
|
||||
--storage-location=[LOCATION_ID]
|
||||
|
||||
To disable default sink for the Logs Router for an organization, run:
|
||||
|
||||
$ gcloud logging settings update --organization=[ORGANIZATION_ID] \
|
||||
--disable-default-sink=true
|
||||
|
||||
To enable default sink for the Logs Router for an organization, run:
|
||||
|
||||
$ gcloud logging settings update --organization=[ORGANIZATION_ID] \
|
||||
--disable-default-sink=false
|
||||
|
||||
REQUIRED FLAGS
|
||||
Exactly one of these must be specified:
|
||||
|
||||
--folder=FOLDER_ID
|
||||
Folder to update Logs Router settings for.
|
||||
|
||||
--organization=ORGANIZATION_ID
|
||||
Organization to update Logs Router settings for.
|
||||
|
||||
OPTIONAL FLAGS
|
||||
--disable-default-sink
|
||||
Enable or disable Default sink for the Default bucket. Specify
|
||||
--no-disable-default-sink to enable a disabled Default sink. Note: It
|
||||
only applies to the newly created projects and will not affect the
|
||||
projects created before.
|
||||
|
||||
--storage-location=STORAGE_LOCATION
|
||||
Update the storage location for Default bucket and Required bucket.
|
||||
Note: It only applies to the newly created projects and will not affect
|
||||
the projects created before.
|
||||
|
||||
At most one of these can be specified:
|
||||
|
||||
--clear-kms-key
|
||||
Disable CMEK for the Logs Router by clearing out Cloud KMS cryptokey
|
||||
in the organization's CMEK settings.
|
||||
|
||||
Key resource - The Cloud KMS (Key Management Service) cryptokey that
|
||||
will be used to protect the logs being processed by the Cloud Logging
|
||||
Logs Router. The Cloud KMS CryptoKey Encrypter/Decryper role must be
|
||||
assigned to the Cloud Logging Logs Router service account. The arguments
|
||||
in this group can be used to specify the attributes of this resource.
|
||||
|
||||
--kms-key-name=KMS_KEY_NAME
|
||||
ID of the key or fully qualified identifier for the key. To set the
|
||||
kms-key attribute:
|
||||
▫ provide the argument --kms-key-name on the command line.
|
||||
|
||||
This flag argument must be specified if any of the other arguments
|
||||
in this group are specified.
|
||||
|
||||
--kms-keyring=KMS_KEYRING
|
||||
The KMS keyring of the key. To set the kms-keyring attribute:
|
||||
▫ provide the argument --kms-key-name on the command line with a
|
||||
fully specified name;
|
||||
▫ provide the argument --kms-keyring on the command line.
|
||||
|
||||
--kms-location=KMS_LOCATION
|
||||
The Cloud location for the key. To set the kms-location attribute:
|
||||
▫ provide the argument --kms-key-name on the command line with a
|
||||
fully specified name;
|
||||
▫ provide the argument --kms-location on the command line.
|
||||
|
||||
--kms-project=KMS_PROJECT
|
||||
The Cloud project for the key. To set the kms-project attribute:
|
||||
▫ provide the argument --kms-key-name on the command line with a
|
||||
fully specified name;
|
||||
▫ provide the argument --kms-project on the command line;
|
||||
▫ set the property core/project.
|
||||
|
||||
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 logging settings update
|
||||
|
||||
$ gcloud beta logging settings update
|
||||
|
||||
Loading…
Add table
Add a link
Reference in a new issue