imjasonh/gcloud-help
1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-20 04:58:26 +00:00
Code Activity

gcloud: Wed Jul 27 08:55:33 UTC 2022

Browse source
This commit is contained in:
Automated 2022-07-27 08:55:33 +00:00
parent 380c3aa29f
commit 3513fd1c11
Failed to extract signature
171 changed files with 3989 additions and 448 deletions
Download patch file Download diff file Expand all files Collapse all files

43
gcloud/beta/datastream/streams/create
View file

@ -8,8 +8,7 @@ SYNOPSIS
| --backfill-all --mysql-excluded-objects=MYSQL_EXCLUDED_OBJECTS
| --oracle-excluded-objects=ORACLE_EXCLUDED_OBJECTS)
(--destination-name=DESTINATION_NAME
(--bigquery-destination-config=BIGQUERY_DESTINATION_CONFIG
| --gcs-destination-config=GCS_DESTINATION_CONFIG))
--gcs-destination-config=GCS_DESTINATION_CONFIG)
(--source-name=SOURCE_NAME (--mysql-source-config=MYSQL_SOURCE_CONFIG
| --oracle-source-config=ORACLE_SOURCE_CONFIG))
[--labels=[KEY=VALUE,...]] [--force | --validate-only]
@ -109,37 +108,21 @@ REQUIRED FLAGS
connection_profile. To set the connection_profile attribute:
▫ provide the argument --destination-name on the command line.
Exactly one of these must be specified:
--gcs-destination-config=GCS_DESTINATION_CONFIG
Path to a YAML (or JSON) file containing the configuration for Google
Cloud Storage Destination Config.
--bigquery-destination-config=BIGQUERY_DESTINATION_CONFIG
Path to a YAML (or JSON) file containing the configuration for
Google BigQuery Destination Config.
The JSON file is formatted as follows:
The JSON file is formatted as follows:
{
"path": "some/path",
"file_rotation_mb":5,
"file_rotation_interval":"15s",
"avro_file_format": {}
}
{
"source_hierarchy_datasets": {
"dataset_template": {
"location": "us-central1",
"dataset_id_prefix": "my_prefix",
"kms_key_name": "projects/{project}/locations/{location}/keyRings/{key_ring}/cryptoKeys/{cryptoKey}"
}
},
"data_freshness": 3600
}
--gcs-destination-config=GCS_DESTINATION_CONFIG
Path to a YAML (or JSON) file containing the configuration for
Google Cloud Storage Destination Config.
The JSON file is formatted as follows:
{
"path": "some/path",
"file_rotation_mb":5,
"file_rotation_interval":"15s",
"avro_file_format": {}
}
This flag must be specified if any of the other arguments in this
group are specified.
This must be specified.

42
gcloud/beta/datastream/streams/update
View file

@ -10,8 +10,7 @@ SYNOPSIS
| --oracle-excluded-objects=ORACLE_EXCLUDED_OBJECTS]
[--clear-labels | --remove-labels=[KEY,...]]
[--destination-name=DESTINATION_NAME
: --bigquery-destination-config=BIGQUERY_DESTINATION_CONFIG
| --gcs-destination-config=GCS_DESTINATION_CONFIG]
: --gcs-destination-config=GCS_DESTINATION_CONFIG]
[--force | --validate-only]
[--source-name=SOURCE_NAME : --mysql-source-config=MYSQL_SOURCE_CONFIG
| --oracle-source-config=ORACLE_SOURCE_CONFIG] [GCLOUD_WIDE_FLAG ...]
@ -145,37 +144,18 @@ FLAGS
connection_profile. To set the connection_profile attribute:
▸ provide the argument --destination-name on the command line.
At most one of these can be specified:
--gcs-destination-config=GCS_DESTINATION_CONFIG
Path to a YAML (or JSON) file containing the configuration for Google
Cloud Storage Destination Config.
--bigquery-destination-config=BIGQUERY_DESTINATION_CONFIG
Path to a YAML (or JSON) file containing the configuration for Google
BigQuery Destination Config.
The JSON file is formatted as follows:
The JSON file is formatted as follows:
{
"source_hierarchy_datasets": {
"dataset_template": {
"location": "us-central1",
"dataset_id_prefix": "my_prefix",
"kms_key_name": "projects/{project}/locations/{location}/keyRings/{key_ring}/cryptoKeys/{cryptoKey}"
}
},
"data_freshness": 3600
}
--gcs-destination-config=GCS_DESTINATION_CONFIG
Path to a YAML (or JSON) file containing the configuration for Google
Cloud Storage Destination Config.
The JSON file is formatted as follows:
{
"path": "some/path",
"file_rotation_mb":5,
"file_rotation_interval":"15s",
"avro_file_format": {}
}
{
"path": "some/path",
"file_rotation_mb":5,
"file_rotation_interval":"15s",
"avro_file_format": {}
}
At most one of these can be specified: