google-cloud-batch-v1 1.8.0 → 1.8.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +4 -4
- data/lib/google/cloud/batch/v1/version.rb +1 -1
- data/proto_docs/google/cloud/batch/v1/job.rb +24 -12
- metadata +1 -1
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 0ccfedfd765f5bade74f111e88cfe2be55b7cc2159ddd271e8282b7473127696
|
|
4
|
+
data.tar.gz: 67f113b402cd1931e0f95139fd5c474cc985888121e427fd8a4e22ef5deb0674
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 6fadffa82a9feb79ef4f540d4fe8006a9bc9c7bf94f0f3b449bc9b4d95d4d9a1b24bc2fab685a5b23dd8932de65c81a820e074aca272cb61dcb50eefebd117b7
|
|
7
|
+
data.tar.gz: dfd4500f7ecc1a3e1a8353b4e08ed5f1424b4634559e9926e3d9b0a8ba2cad1e6a2a389ac6fce7642786bd9b11cae32eb00be071ed9cff281ef67e04ed6fdccd
|
|
@@ -361,20 +361,32 @@ module Google
|
|
|
361
361
|
|
|
362
362
|
# @!attribute [rw] allowed_locations
|
|
363
363
|
# @return [::Array<::String>]
|
|
364
|
-
# A list of
|
|
364
|
+
# A list of location names that are allowed for the job's VMs formatted
|
|
365
|
+
# as URLs. Each location can be a region or a zone, but you can only
|
|
366
|
+
# specify one region or multiple zones in one region per job. For example,
|
|
367
|
+
# `["regions/us-central1"]` allow VMs in any zones in region
|
|
368
|
+
# `us-central1`, and `["zones/us-central1-a", "zones/us-central1-c"]`
|
|
369
|
+
# only allow VMs in zones `us-central1-a` and `us-central1-c`. However,
|
|
370
|
+
# `["regions/us-central1", "zones/us-central1-a", "zones/us-central1-b",
|
|
371
|
+
# "zones/us-west1-a"]` causes an error because it contains multiple regions
|
|
372
|
+
# (`us-central1` and `us-west1`).
|
|
365
373
|
#
|
|
366
|
-
#
|
|
367
|
-
#
|
|
368
|
-
# For example,
|
|
369
|
-
# ["regions/us-central1"] allow VMs in any zones in region us-central1.
|
|
370
|
-
# ["zones/us-central1-a", "zones/us-central1-c"] only allow VMs
|
|
371
|
-
# in zones us-central1-a and us-central1-c.
|
|
374
|
+
# The specified region or zones must be in the same region in
|
|
375
|
+
# which the job is created starting on the following dates:
|
|
372
376
|
#
|
|
373
|
-
#
|
|
374
|
-
#
|
|
375
|
-
#
|
|
376
|
-
#
|
|
377
|
-
#
|
|
377
|
+
# + For projects that have successfully submitted before
|
|
378
|
+
# July 31, 2026 at least one job that uses the
|
|
379
|
+
# `allowedLocations[]` field with any region or zones
|
|
380
|
+
# outside of the job's location, the changes are starting
|
|
381
|
+
# on _June 30, 2027_.
|
|
382
|
+
#
|
|
383
|
+
# + For all other projects, the changes are starting on
|
|
384
|
+
# _July 31, 2026_.
|
|
385
|
+
#
|
|
386
|
+
# For example, for job `projects/123/locations/us-central1/jobs/jobid`,
|
|
387
|
+
# the specified region or zones must be in `us-central1`. Using a
|
|
388
|
+
# different region (e.g. `regions/us-west1`) or a zone not in
|
|
389
|
+
# `us-central1` (e.g. `zones/us-west1-a`) causes an error.
|
|
378
390
|
class LocationPolicy
|
|
379
391
|
include ::Google::Protobuf::MessageExts
|
|
380
392
|
extend ::Google::Protobuf::MessageExts::ClassMethods
|