@@ -190,6 +190,36 @@ def update!(**args)
190190 end
191191 end
192192
193+ # Describes the project/location configuration of Cloud Scheduler Resources.
194+ class CmekConfig
195+ include Google ::Apis ::Core ::Hashable
196+
197+ # Optional. Resource name of the Cloud KMS key, of the form `projects/PROJECT_ID/
198+ # locations/LOCATION_ID/keyRings/KEY_RING_ID/cryptoKeys/KEY_ID`, that will be
199+ # used to encrypt Jobs in the region. Setting this as blank will turn off CMEK
200+ # encryption.
201+ # Corresponds to the JSON property `kmsKeyName`
202+ # @return [String]
203+ attr_accessor :kms_key_name
204+
205+ # Identifier. The config resource name which includes the project and location
206+ # and must end in 'cmekConfig', in the format projects/PROJECT_ID/locations/
207+ # LOCATION_ID/cmekConfig`
208+ # Corresponds to the JSON property `name`
209+ # @return [String]
210+ attr_accessor :name
211+
212+ def initialize ( **args )
213+ update! ( **args )
214+ end
215+
216+ # Update properties of this object
217+ def update! ( **args )
218+ @kms_key_name = args [ :kms_key_name ] if args . key? ( :kms_key_name )
219+ @name = args [ :name ] if args . key? ( :name )
220+ end
221+ end
222+
193223 # A generic empty message that you can re-use to avoid defining duplicated empty
194224 # messages in your APIs. A typical example is to use it as the request or the
195225 # response type of an API method. For instance: service Foo ` rpc Bar(google.
@@ -344,12 +374,13 @@ class Job
344374 # The job name. For example: `projects/PROJECT_ID/locations/LOCATION_ID/jobs/
345375 # JOB_ID`. * `PROJECT_ID` can contain letters ([A-Za-z]), numbers ([0-9]),
346376 # hyphens (-), colons (:), or periods (.). For more information, see [
347- # Identifying projects](https://cloud.google.com/resource-manager/docs/creating-
348- # managing-projects#identifying_projects) * `LOCATION_ID` is the canonical ID
349- # for the job's location. The list of available locations can be obtained by
350- # calling ListLocations. For more information, see https://cloud.google.com/
351- # about/locations/. * `JOB_ID` can contain only letters ([A-Za-z]), numbers ([0-
352- # 9]), hyphens (-), or underscores (_). The maximum length is 500 characters.
377+ # Identifying projects](/resource-manager/docs/creating-managing-projects#
378+ # identifying_projects) * `LOCATION_ID` is the canonical ID for the job's
379+ # location. The list of available locations can be obtained by calling [
380+ # locations.list](/scheduler/docs/reference/rest/v1/projects.locations/list).
381+ # For more information, see [Cloud Scheduler locations](/scheduler/docs/
382+ # locations). * `JOB_ID` can contain only letters ([A-Za-z]), numbers ([0-9]),
383+ # hyphens (-), or underscores (_). The maximum length is 500 characters.
353384 # Corresponds to the JSON property `name`
354385 # @return [String]
355386 attr_accessor :name
@@ -361,10 +392,10 @@ class Job
361392 attr_accessor :pubsub_target
362393
363394 # Settings that determine the retry behavior. For more information, see [Retry
364- # jobs](https://cloud.google.com/ scheduler/docs/configuring/retry-jobs). By
365- # default, if a job does not complete successfully (meaning that an
366- # acknowledgement is not received from the handler, then it will be retried with
367- # exponential backoff according to the settings in RetryConfig.
395+ # jobs](/ scheduler/docs/configuring/retry-jobs). By default, if a job does not
396+ # complete successfully (meaning that an acknowledgement is not received from
397+ # the handler, then it will be retried with exponential backoff according to the
398+ # settings in RetryConfig.
368399 # Corresponds to the JSON property `retryConfig`
369400 # @return [Google::Apis::CloudschedulerV1::RetryConfig]
370401 attr_accessor :retry_config
@@ -379,19 +410,19 @@ class Job
379410 # Required, except when used with UpdateJob. Describes the schedule on which the
380411 # job will be executed. The schedule can be either of the following types: * [
381412 # Crontab](https://en.wikipedia.org/wiki/Cron#Overview) * English-like [schedule]
382- # (https://cloud.google.com/ scheduler/docs/configuring/cron-job-schedules) As a
383- # general rule, execution ` n + 1` of a job will not begin until execution `n`
384- # has finished. Cloud Scheduler will never allow two simultaneously outstanding
385- # executions. For example, this implies that if the `n+1`th execution is
386- # scheduled to run at 16: 00 but the `n`th execution takes until 16:15, the `n+1`
387- # th execution will not start until `16:15`. A scheduled start time will be
388- # delayed if the previous execution has not ended when its scheduled time occurs.
389- # If retry_count > 0 and a job attempt fails, the job will be tried a total of
390- # retry_count times, with exponential backoff, until the next scheduled start
391- # time. If retry_count is 0, a job attempt will not be retried if it fails.
392- # Instead the Cloud Scheduler system will wait for the next scheduled execution
393- # time. Setting retry_count to 0 does not prevent failed jobs from running
394- # according to schedule after the failure.
413+ # (/ scheduler/docs/configuring/cron-job-schedules) As a general rule, execution `
414+ # n + 1` of a job will not begin until execution `n` has finished. Cloud
415+ # Scheduler will never allow two simultaneously outstanding executions. For
416+ # example, this implies that if the `n+1`th execution is scheduled to run at 16:
417+ # 00 but the `n`th execution takes until 16:15, the `n+1`th execution will not
418+ # start until `16:15`. A scheduled start time will be delayed if the previous
419+ # execution has not ended when its scheduled time occurs. If retry_count > 0 and
420+ # a job attempt fails, the job will be tried a total of retry_count times, with
421+ # exponential backoff, until the next scheduled start time. If retry_count is 0,
422+ # a job attempt will not be retried if it fails. Instead the Cloud Scheduler
423+ # system will wait for the next scheduled execution time. Setting retry_count to
424+ # 0 does not prevent failed jobs from running according to schedule after the
425+ # failure.
395426 # Corresponds to the JSON property `schedule`
396427 # @return [String]
397428 attr_accessor :schedule
@@ -905,10 +936,10 @@ def update!(**args)
905936 end
906937
907938 # Settings that determine the retry behavior. For more information, see [Retry
908- # jobs](https://cloud.google.com/ scheduler/docs/configuring/retry-jobs). By
909- # default, if a job does not complete successfully (meaning that an
910- # acknowledgement is not received from the handler, then it will be retried with
911- # exponential backoff according to the settings in RetryConfig.
939+ # jobs](/ scheduler/docs/configuring/retry-jobs). By default, if a job does not
940+ # complete successfully (meaning that an acknowledgement is not received from
941+ # the handler, then it will be retried with exponential backoff according to the
942+ # settings in RetryConfig.
912943 class RetryConfig
913944 include Google ::Apis ::Core ::Hashable
914945
@@ -921,9 +952,9 @@ class RetryConfig
921952 # The time between retries will double `max_doublings` times. A job's retry
922953 # interval starts at min_backoff_duration, then doubles `max_doublings` times,
923954 # then increases linearly, and finally retries at intervals of
924- # max_backoff_duration up to retry_count times. For examples, see [Retry jobs](
925- # https://cloud.google.com/ scheduler/docs/configuring/retry-jobs#max-doublings).
926- # The default value of this field is 5.
955+ # max_backoff_duration up to retry_count times. For examples, see [Retry jobs](/
956+ # scheduler/docs/configuring/retry-jobs#max-doublings). The default value of
957+ # this field is 5.
927958 # Corresponds to the JSON property `maxDoublings`
928959 # @return [Fixnum]
929960 attr_accessor :max_doublings
0 commit comments