From 0fe7a90fdc5356cc453e4c9c6f0b88a0c10e49d5 Mon Sep 17 00:00:00 2001 From: awstools Date: Mon, 8 Oct 2018 13:00:21 -0700 Subject: [PATCH] Update to latest models --- .../next-release/api-change-iot-23140.json | 5 +++ .../api-change-iotjobsdata-97872.json | 5 +++ .../iot-jobs-data/2017-09-29/service-2.json | 22 +++++++++++- botocore/data/iot/2015-05-28/service-2.json | 36 +++++++++++++++++-- 4 files changed, 64 insertions(+), 4 deletions(-) create mode 100644 .changes/next-release/api-change-iot-23140.json create mode 100644 .changes/next-release/api-change-iotjobsdata-97872.json diff --git a/.changes/next-release/api-change-iot-23140.json b/.changes/next-release/api-change-iot-23140.json new file mode 100644 index 0000000000..18027d03db --- /dev/null +++ b/.changes/next-release/api-change-iot-23140.json @@ -0,0 +1,5 @@ +{ + "category": "``iot``", + "type": "api-change", + "description": "Update iot client to latest version" +} diff --git a/.changes/next-release/api-change-iotjobsdata-97872.json b/.changes/next-release/api-change-iotjobsdata-97872.json new file mode 100644 index 0000000000..d2cbed88d0 --- /dev/null +++ b/.changes/next-release/api-change-iotjobsdata-97872.json @@ -0,0 +1,5 @@ +{ + "category": "``iot-jobs-data``", + "type": "api-change", + "description": "Update iot-jobs-data client to latest version" +} diff --git a/botocore/data/iot-jobs-data/2017-09-29/service-2.json b/botocore/data/iot-jobs-data/2017-09-29/service-2.json index 8fb28a2b97..935bb64e0f 100644 --- a/botocore/data/iot-jobs-data/2017-09-29/service-2.json +++ b/botocore/data/iot-jobs-data/2017-09-29/service-2.json @@ -83,6 +83,8 @@ } }, "shapes":{ + "ApproximateSecondsBeforeTimedOut":{"type":"long"}, + "BinaryBlob":{"type":"blob"}, "CertificateValidationException":{ "type":"structure", "members":{ @@ -243,6 +245,10 @@ "shape":"LastUpdatedAt", "documentation":"

The time, in milliseconds since the epoch, when the job execution was last updated.

" }, + "approximateSecondsBeforeTimedOut":{ + "shape":"ApproximateSecondsBeforeTimedOut", + "documentation":"

The estimated number of seconds that remain before the job execution status will be changed to TIMED_OUT.

" + }, "versionNumber":{ "shape":"VersionNumber", "documentation":"

The version of the job execution. Job execution versions are incremented each time they are updated by a device.

" @@ -283,6 +289,7 @@ "IN_PROGRESS", "SUCCEEDED", "FAILED", + "TIMED_OUT", "REJECTED", "REMOVED", "CANCELED" @@ -368,6 +375,10 @@ "statusDetails":{ "shape":"DetailsMap", "documentation":"

A collection of name/value pairs that describe the status of the job execution. If not specified, the statusDetails are unchanged.

" + }, + "stepTimeoutInMinutes":{ + "shape":"StepTimeoutInMinutes", + "documentation":"

Specifies the amount of time this device has to finish execution of this job. If the job execution status is not set to a terminal state before this timer expires, or before the timer is reset (by calling UpdateJobExecution, setting the status to IN_PROGRESS and specifying a new timeout value in field stepTimeoutInMinutes) the job execution status will be automatically set to TIMED_OUT. Note that setting this timeout has no effect on that job execution timeout which may have been specified when the job was created (CreateJob using field timeoutConfig).

" } } }, @@ -381,6 +392,7 @@ } }, "StartedAt":{"type":"long"}, + "StepTimeoutInMinutes":{"type":"long"}, "TerminalStateException":{ "type":"structure", "members":{ @@ -401,7 +413,11 @@ "members":{ "message":{ "shape":"errorMessage", - "documentation":"

The message for the exception.

" + "documentation":"

The message associated with the exception.

" + }, + "payload":{ + "shape":"BinaryBlob", + "documentation":"

The payload associated with the exception.

" } }, "documentation":"

The rate exceeds the limit.

", @@ -436,6 +452,10 @@ "shape":"DetailsMap", "documentation":"

Optional. A collection of name/value pairs that describe the status of the job execution. If not specified, the statusDetails are unchanged.

" }, + "stepTimeoutInMinutes":{ + "shape":"StepTimeoutInMinutes", + "documentation":"

Specifies the amount of time this device has to finish execution of this job. If the job execution status is not set to a terminal state before this timer expires, or before the timer is reset (by again calling UpdateJobExecution, setting the status to IN_PROGRESS and specifying a new timeout value in this field) the job execution status will be automatically set to TIMED_OUT. Note that setting or resetting this timeout has no effect on that job execution timeout which may have been specified when the job was created (CreateJob using field timeoutConfig).

" + }, "expectedVersion":{ "shape":"ExpectedVersion", "documentation":"

Optional. The expected current version of the job execution. Each time you update the job execution, its version is incremented. If the version of the job execution stored in Jobs does not match, the update is rejected with a VersionMismatch error, and an ErrorResponse that contains the current job execution status data is returned. (This makes it unnecessary to perform a separate DescribeJobExecution request in order to obtain the job execution status data.)

" diff --git a/botocore/data/iot/2015-05-28/service-2.json b/botocore/data/iot/2015-05-28/service-2.json index 369c4cdcd3..26417c5bc0 100644 --- a/botocore/data/iot/2015-05-28/service-2.json +++ b/botocore/data/iot/2015-05-28/service-2.json @@ -2804,6 +2804,7 @@ }, "documentation":"

Contains information that allowed the authorization.

" }, + "ApproximateSecondsBeforeTimedOut":{"type":"long"}, "AscendingOrder":{"type":"boolean"}, "AssociateTargetsWithJobRequest":{ "type":"structure", @@ -4043,6 +4044,10 @@ "jobExecutionsRolloutConfig":{ "shape":"JobExecutionsRolloutConfig", "documentation":"

Allows you to create a staged rollout of the job.

" + }, + "timeoutConfig":{ + "shape":"TimeoutConfig", + "documentation":"

Specifies the amount of time each device has to finish its execution of the job. The timer is started when the job execution status is set to IN_PROGRESS. If the job execution status is not set to another terminal state before the time expires, it will be automatically set to TIMED_OUT.

" } } }, @@ -5185,7 +5190,7 @@ "members":{ "endpointType":{ "shape":"EndpointType", - "documentation":"

The endpoint type (such as iot:Data, iot:CredentialProvider and iot:Jobs).

", + "documentation":"

The endpoint type. Valid endpoint types include:

", "location":"querystring", "locationName":"endpointType" } @@ -6355,6 +6360,7 @@ }, "InProgressChecksCount":{"type":"integer"}, "InProgressThings":{"type":"integer"}, + "InProgressTimeoutInMinutes":{"type":"long"}, "IndexName":{ "type":"string", "max":128, @@ -6499,7 +6505,7 @@ }, "status":{ "shape":"JobStatus", - "documentation":"

The status of the job, one of IN_PROGRESS, CANCELED, or COMPLETED.

" + "documentation":"

The status of the job, one of IN_PROGRESS, CANCELED, DELETION_IN_PROGRESS or COMPLETED.

" }, "forceCanceled":{ "shape":"Forced", @@ -6540,6 +6546,10 @@ "jobProcessDetails":{ "shape":"JobProcessDetails", "documentation":"

Details about the job process.

" + }, + "timeoutConfig":{ + "shape":"TimeoutConfig", + "documentation":"

Specifies the amount of time each device has to finish its execution of the job. A timer is started when the job execution status is set to IN_PROGRESS. If the job execution status is not set to another terminal state before the timer expires, it will be automatically set to TIMED_OUT.

" } }, "documentation":"

The Job object contains details about a job.

" @@ -6568,7 +6578,7 @@ }, "status":{ "shape":"JobExecutionStatus", - "documentation":"

The status of the job execution (IN_PROGRESS, QUEUED, FAILED, SUCCESS, CANCELED, or REJECTED).

" + "documentation":"

The status of the job execution (IN_PROGRESS, QUEUED, FAILED, SUCCEEDED, TIMED_OUT, CANCELED, or REJECTED).

" }, "forceCanceled":{ "shape":"Forced", @@ -6601,6 +6611,10 @@ "versionNumber":{ "shape":"VersionNumber", "documentation":"

The version of the job execution. Job execution versions are incremented each time they are updated by a device.

" + }, + "approximateSecondsBeforeTimedOut":{ + "shape":"ApproximateSecondsBeforeTimedOut", + "documentation":"

The estimated number of seconds that remain before the job execution status will be changed to TIMED_OUT.

" } }, "documentation":"

The job execution object represents the execution of a job on a particular device.

" @@ -6612,6 +6626,7 @@ "IN_PROGRESS", "SUCCEEDED", "FAILED", + "TIMED_OUT", "REJECTED", "REMOVED", "CANCELED" @@ -6739,6 +6754,10 @@ "numberOfRemovedThings":{ "shape":"RemovedThings", "documentation":"

The number of things that are no longer scheduled to execute the job because they have been deleted or have been removed from the group that was a target of the job.

" + }, + "numberOfTimedOutThings":{ + "shape":"TimedOutThings", + "documentation":"

The number of things whose job execution status is TIMED_OUT.

" } }, "documentation":"

The job process details.

" @@ -10462,6 +10481,17 @@ "error":{"httpStatusCode":429}, "exception":true }, + "TimedOutThings":{"type":"integer"}, + "TimeoutConfig":{ + "type":"structure", + "members":{ + "inProgressTimeoutInMinutes":{ + "shape":"InProgressTimeoutInMinutes", + "documentation":"

Specifies the amount of time, in minutes, this device has to finish execution of this job. A timer is started, or restarted, whenever this job's execution status is specified as IN_PROGRESS with this field populated. If the job execution status is not set to a terminal state before the timer expires, or before another job execution status update is sent with this field populated, the status will be automatically set to TIMED_OUT. Note that setting/resetting this timer has no effect on the job execution timeout timer which may have been specified when the job was created (CreateJobExecution using the field timeoutConfig).

" + } + }, + "documentation":"

Specifies the amount of time each device has to finish its execution of the job. A timer is started when the job execution status is set to IN_PROGRESS. If the job execution status is not set to another terminal state before the timer expires, it will be automatically set to TIMED_OUT.

" + }, "Timestamp":{"type":"timestamp"}, "Token":{ "type":"string",