google-cloud-batch-v1 0.18.1 → 0.18.2

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: a89581df3e75447efb56da31ea63cbbfff56ecd91db8ed93a913356731495d13
4
- data.tar.gz: f5a3ccc0fc8de54f8c03f052db7eebc004050da5a926aac73a8711687c3bb236
3
+ metadata.gz: c9a3a810dd582f7a409705d10e3c87cb9a0dbf67d249b327584b1ac7d9f865b2
4
+ data.tar.gz: 59bc014e61610463889e164df17cac91de4ad5afb244197a6642e6e81e201efd
5
5
  SHA512:
6
- metadata.gz: ad73fac26914fa4273248f1fd793f4510e3c1e5b563e7324c9f052b8faa557f2b729e06263e1da9a8092bc96ed17f42c5bc1370ae0f0e17827e09644d09202e5
7
- data.tar.gz: de6915c91dcf4b1bace5170d5f52ae6e4ed3f9c75b6499c826557fd0829093bcd03c87675e38c5ea43961fd5c174d5c94744c1b79864c662c97038aa2de26b59
6
+ metadata.gz: 2f2446afab1cbe8050d02895496c074aa4d4fb78945777c0518e1e4fd811db1ba08d47f526bfc31a323d77a387eb5a27e20ee25a4a95ee6b71fabd3c06c26a4f
7
+ data.tar.gz: 4ef67ebdc8e9a905c75fb9270034ac82f42422999ad7260dd8691abb681a8aea1a41521502a6c6da5303beb5b8c3e21c80f17024fdfcc68351e71b1782e95eef
@@ -21,7 +21,7 @@ module Google
21
21
  module Cloud
22
22
  module Batch
23
23
  module V1
24
- VERSION = "0.18.1"
24
+ VERSION = "0.18.2"
25
25
  end
26
26
  end
27
27
  end
@@ -376,9 +376,7 @@ module Google
376
376
  # The following image values are supported for a boot disk:
377
377
  #
378
378
  # * `batch-debian`: use Batch Debian images.
379
- # * `batch-centos`: use Batch CentOS images.
380
379
  # * `batch-cos`: use Batch Container-Optimized images.
381
- # * `batch-hpc-centos`: use Batch HPC CentOS images.
382
380
  # * `batch-hpc-rocky`: use Batch HPC Rocky Linux images.
383
381
  # @!attribute [rw] snapshot
384
382
  # @return [::String]
@@ -173,13 +173,24 @@ module Google
173
173
  # provided the index of the runnable will be used for outputs.
174
174
  # @!attribute [rw] ignore_exit_status
175
175
  # @return [::Boolean]
176
- # Normally, a non-zero exit status causes the Task to fail. This flag allows
177
- # execution of other Runnables to continue instead.
176
+ # Normally, a runnable that returns a non-zero exit status fails and causes
177
+ # the task to fail. However, you can set this field to `true` to allow the
178
+ # task to continue executing its other runnables even if this runnable
179
+ # fails.
178
180
  # @!attribute [rw] background
179
181
  # @return [::Boolean]
180
- # This flag allows a Runnable to continue running in the background while the
181
- # Task executes subsequent Runnables. This is useful to provide services to
182
- # other Runnables (or to provide debugging support tools like SSH servers).
182
+ # Normally, a runnable that doesn't exit causes its task to fail. However,
183
+ # you can set this field to `true` to configure a background runnable.
184
+ # Background runnables are allowed continue running in the background while
185
+ # the task executes subsequent runnables. For example, background runnables
186
+ # are useful for providing services to other runnables or providing
187
+ # debugging-support tools like SSH servers.
188
+ #
189
+ # Specifically, background runnables are killed automatically (if they have
190
+ # not already exited) a short time after all foreground runnables have
191
+ # completed. Even though this is likely to result in a non-zero exit status
192
+ # for the background runnable, these automatic kills are not treated as task
193
+ # failures.
183
194
  # @!attribute [rw] always_run
184
195
  # @return [::Boolean]
185
196
  # By default, after a Runnable fails, no further Runnable are executed. This
@@ -207,32 +218,36 @@ module Google
207
218
  # Container runnable.
208
219
  # @!attribute [rw] image_uri
209
220
  # @return [::String]
210
- # The URI to pull the container image from.
221
+ # Required. The URI to pull the container image from.
211
222
  # @!attribute [rw] commands
212
223
  # @return [::Array<::String>]
213
- # Overrides the `CMD` specified in the container. If there is an ENTRYPOINT
214
- # (either in the container image or with the entrypoint field below) then
215
- # commands are appended as arguments to the ENTRYPOINT.
224
+ # Required for some container images. Overrides the `CMD` specified in the
225
+ # container. If there is an `ENTRYPOINT` (either in the container image or
226
+ # with the `entrypoint` field below) then these commands are appended as
227
+ # arguments to the `ENTRYPOINT`.
216
228
  # @!attribute [rw] entrypoint
217
229
  # @return [::String]
218
- # Overrides the `ENTRYPOINT` specified in the container.
230
+ # Required for some container images. Overrides the `ENTRYPOINT` specified
231
+ # in the container.
219
232
  # @!attribute [rw] volumes
220
233
  # @return [::Array<::String>]
221
234
  # Volumes to mount (bind mount) from the host machine files or directories
222
- # into the container, formatted to match docker run's --volume option,
223
- # e.g. /foo:/bar, or /foo:/bar:ro
235
+ # into the container, formatted to match `--volume` option for the
236
+ # `docker run` command&mdash;for example, `/foo:/bar` or `/foo:/bar:ro`.
224
237
  #
225
238
  # If the `TaskSpec.Volumes` field is specified but this field is not, Batch
226
239
  # will mount each volume from the host machine to the container with the
227
240
  # same mount path by default. In this case, the default mount option for
228
- # containers will be read-only (ro) for existing persistent disks and
229
- # read-write (rw) for other volume types, regardless of the original mount
230
- # options specified in `TaskSpec.Volumes`. If you need different mount
231
- # settings, you can explicitly configure them in this field.
241
+ # containers will be read-only (`ro`) for existing persistent disks and
242
+ # read-write (`rw`) for other volume types, regardless of the original
243
+ # mount options specified in `TaskSpec.Volumes`. If you need different
244
+ # mount settings, you can explicitly configure them in this field.
232
245
  # @!attribute [rw] options
233
246
  # @return [::String]
234
- # Arbitrary additional options to include in the "docker run" command when
235
- # running this container, e.g. "--network host".
247
+ # Required for some container images. Arbitrary additional options to
248
+ # include in the `docker run` command when running this container&mdash;for
249
+ # example, `--network host`. For the `--volume` option, use the `volumes`
250
+ # field for the container.
236
251
  # @!attribute [rw] block_external_network
237
252
  # @return [::Boolean]
238
253
  # If set to true, external network access to and from container will be
@@ -301,30 +316,33 @@ module Google
301
316
  # Script runnable.
302
317
  # @!attribute [rw] path
303
318
  # @return [::String]
304
- # Script file path on the host VM.
319
+ # The path to a script file that is accessible from the host VM(s).
305
320
  #
306
- # To specify an interpreter, please add a `#!<interpreter>`(also known as
307
- # [shebang line](https://en.wikipedia.org/wiki/Shebang_(Unix))) as the
308
- # first line of the file.(For example, to execute the script using bash,
309
- # `#!/bin/bash` should be the first line of the file. To execute the
310
- # script using`Python3`, `#!/usr/bin/env python3` should be the first
311
- # line of the file.) Otherwise, the file will by default be executed by
312
- # `/bin/sh`.
321
+ # Unless the script file supports the default `#!/bin/sh` shell
322
+ # interpreter, you must specify an interpreter by including a
323
+ # [shebang line](https://en.wikipedia.org/wiki/Shebang_(Unix) as the
324
+ # first line of the file. For example, to execute the script using bash,
325
+ # include `#!/bin/bash` as the first line of the file. Alternatively,
326
+ # to execute the script using Python3, include `#!/usr/bin/env python3`
327
+ # as the first line of the file.
313
328
  # @!attribute [rw] text
314
329
  # @return [::String]
315
- # Shell script text.
330
+ # The text for a script.
316
331
  #
317
- # To specify an interpreter, please add a `#!<interpreter>\n` at the
318
- # beginning of the text.(For example, to execute the script using bash,
319
- # `#!/bin/bash\n` should be added. To execute the script using`Python3`,
320
- # `#!/usr/bin/env python3\n` should be added.) Otherwise, the script will
321
- # by default be executed by `/bin/sh`.
332
+ # Unless the script text supports the default `#!/bin/sh` shell
333
+ # interpreter, you must specify an interpreter by including a
334
+ # [shebang line](https://en.wikipedia.org/wiki/Shebang_(Unix) at the
335
+ # beginning of the text. For example, to execute the script using bash,
336
+ # include `#!/bin/bash\n` at the beginning of the text. Alternatively,
337
+ # to execute the script using Python3, include `#!/usr/bin/env python3\n`
338
+ # at the beginning of the text.
322
339
  class Script
323
340
  include ::Google::Protobuf::MessageExts
324
341
  extend ::Google::Protobuf::MessageExts::ClassMethods
325
342
  end
326
343
 
327
- # Barrier runnable blocks until all tasks in a taskgroup reach it.
344
+ # A barrier runnable automatically blocks the execution of subsequent
345
+ # runnables until all the tasks in the task group reach the barrier.
328
346
  # @!attribute [rw] name
329
347
  # @return [::String]
330
348
  # Barriers are identified by their index in runnable list.
@@ -347,16 +365,16 @@ module Google
347
365
  # Spec of a task
348
366
  # @!attribute [rw] runnables
349
367
  # @return [::Array<::Google::Cloud::Batch::V1::Runnable>]
350
- # The sequence of scripts or containers to run for this Task. Each Task using
351
- # this TaskSpec executes its list of runnables in order. The Task succeeds if
352
- # all of its runnables either exit with a zero status or any that exit with a
353
- # non-zero status have the ignore_exit_status flag.
368
+ # Required. The sequence of one or more runnables (executable scripts,
369
+ # executable containers, and/or barriers) for each task in this task group to
370
+ # run. Each task runs this list of runnables in order. For a task to succeed,
371
+ # all of its script and container runnables each must meet at least one of
372
+ # the following conditions:
354
373
  #
355
- # Background runnables are killed automatically (if they have not already
356
- # exited) a short time after all foreground runnables have completed. Even
357
- # though this is likely to result in a non-zero exit status for the
358
- # background runnable, these automatic kills are not treated as Task
359
- # failures.
374
+ # + The runnable exited with a zero status.
375
+ # + The runnable didn't finish, but you enabled its `background` subfield.
376
+ # + The runnable exited with a non-zero status, but you enabled its
377
+ # `ignore_exit_status` subfield.
360
378
  # @!attribute [rw] compute_resource
361
379
  # @return [::Google::Cloud::Batch::V1::ComputeResource]
362
380
  # ComputeResource requirements.
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: google-cloud-batch-v1
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.18.1
4
+ version: 0.18.2
5
5
  platform: ruby
6
6
  authors:
7
7
  - Google LLC
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2024-08-07 00:00:00.000000000 Z
11
+ date: 2024-08-22 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: gapic-common