Skip to content

Commit

Permalink
Update models for release
Browse files Browse the repository at this point in the history
  • Loading branch information
aws-sdk-php-automation committed Jan 3, 2019
1 parent e9a22aa commit e5f6a67
Show file tree
Hide file tree
Showing 8 changed files with 80 additions and 31 deletions.
7 changes: 7 additions & 0 deletions .changes/3.82.5
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
[
{
"type": "api-change",
"category": "IoTAnalytics",
"description": "ListDatasetContents now has a filter to limit results by date scheduled."
}
]
4 changes: 4 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,9 @@
# CHANGELOG

## next release

* `Aws\IoTAnalytics` - ListDatasetContents now has a filter to limit results by date scheduled.

## 3.82.4 - 2019-01-03

* `Aws\OpsWorksCM` - Documentation updates for opsworkscm
Expand Down
26 changes: 26 additions & 0 deletions src/data/endpoints.json
Original file line number Diff line number Diff line change
Expand Up @@ -1111,6 +1111,18 @@
"us-west-2" : { }
}
},
"fsx" : {
"defaults" : {
"protocols" : [ "https" ],
"sslCommonName" : "fsx.us-west-2.amazonaws.com"
},
"endpoints" : {
"eu-west-1" : { },
"us-east-1" : { },
"us-east-2" : { },
"us-west-2" : { }
}
},
"gamelift" : {
"endpoints" : {
"ap-northeast-1" : { },
Expand Down Expand Up @@ -1762,6 +1774,20 @@
"us-east-1" : { }
}
},
"route53resolver" : {
"defaults" : {
"protocols" : [ "http", "https" ]
},
"endpoints" : {
"ap-northeast-1" : { },
"ap-southeast-1" : { },
"ap-southeast-2" : { },
"eu-west-1" : { },
"us-east-1" : { },
"us-east-2" : { },
"us-west-2" : { }
}
},
"runtime.lex" : {
"defaults" : {
"credentialScope" : {
Expand Down
2 changes: 1 addition & 1 deletion src/data/endpoints.json.php

Large diffs are not rendered by default.

10 changes: 10 additions & 0 deletions src/data/iotanalytics/2017-11-27/api-2.json
Original file line number Diff line number Diff line change
Expand Up @@ -1404,6 +1404,16 @@
"shape":"MaxResults",
"location":"querystring",
"locationName":"maxResults"
},
"scheduledOnOrAfter":{
"shape":"Timestamp",
"location":"querystring",
"locationName":"scheduledOnOrAfter"
},
"scheduledBefore":{
"shape":"Timestamp",
"location":"querystring",
"locationName":"scheduledBefore"
}
}
},
Expand Down
2 changes: 1 addition & 1 deletion src/data/iotanalytics/2017-11-27/api-2.json.php

Large diffs are not rendered by default.

58 changes: 30 additions & 28 deletions src/data/iotanalytics/2017-11-27/docs-2.json
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@
"CancelPipelineReprocessing": "<p>Cancels the reprocessing of data through the pipeline.</p>",
"CreateChannel": "<p>Creates a channel. A channel collects data from an MQTT topic and archives the raw, unprocessed messages before publishing the data to a pipeline.</p>",
"CreateDataset": "<p>Creates a data set. A data set stores data retrieved from a data store by applying a \"queryAction\" (a SQL query) or a \"containerAction\" (executing a containerized application). This operation creates the skeleton of a data set. The data set can be populated manually by calling \"CreateDatasetContent\" or automatically according to a \"trigger\" you specify.</p>",
"CreateDatasetContent": "<p>Creates the content of a data set by applying a SQL action.</p>",
"CreateDatasetContent": "<p>Creates the content of a data set by applying a \"queryAction\" (a SQL query) or a \"containerAction\" (executing a containerized application).</p>",
"CreateDatastore": "<p>Creates a data store, which is a repository for messages.</p>",
"CreatePipeline": "<p>Creates a pipeline. A pipeline consumes messages from one or more channels and allows you to process the messages before storing them in a data store.</p>",
"DeleteChannel": "<p>Deletes the specified channel.</p>",
Expand Down Expand Up @@ -84,7 +84,7 @@
"DeviceRegistryEnrichActivity$thingName": "<p>The name of the IoT device whose registry information is added to the message.</p>",
"DeviceShadowEnrichActivity$attribute": "<p>The name of the attribute that is added to the message.</p>",
"DeviceShadowEnrichActivity$thingName": "<p>The name of the IoT device whose shadow information is added to the message.</p>",
"MathActivity$attribute": "<p>The name of the attribute that will contain the result of the math operation.</p>"
"MathActivity$attribute": "<p>The name of the attribute that contains the result of the math operation.</p>"
}
},
"AttributeNameMapping": {
Expand Down Expand Up @@ -260,7 +260,7 @@
}
},
"DatasetAction": {
"base": "<p>A \"DatasetAction\" object specifying the query that creates the data set content.</p>",
"base": "<p>A \"DatasetAction\" object that specifies how data set contents are automatically created.</p>",
"refs": {
"DatasetActions$member": null
}
Expand Down Expand Up @@ -306,23 +306,23 @@
}
},
"DatasetContentDeliveryDestination": {
"base": null,
"base": "<p>The destination to which data set contents are delivered.</p>",
"refs": {
"DatasetContentDeliveryRule$destination": null
"DatasetContentDeliveryRule$destination": "<p>The destination to which data set contents are delivered.</p>"
}
},
"DatasetContentDeliveryRule": {
"base": null,
"base": "<p>When data set contents are created they are delivered to destination specified here.</p>",
"refs": {
"DatasetContentDeliveryRules$member": null
}
},
"DatasetContentDeliveryRules": {
"base": null,
"refs": {
"CreateDatasetRequest$contentDeliveryRules": null,
"Dataset$contentDeliveryRules": null,
"UpdateDatasetRequest$contentDeliveryRules": null
"CreateDatasetRequest$contentDeliveryRules": "<p>When data set contents are created they are delivered to destinations specified here.</p>",
"Dataset$contentDeliveryRules": "<p>When data set contents are created they are delivered to destinations specified here.</p>",
"UpdateDatasetRequest$contentDeliveryRules": "<p>When data set contents are created they are delivered to destinations specified here.</p>"
}
},
"DatasetContentState": {
Expand Down Expand Up @@ -360,7 +360,7 @@
}
},
"DatasetContentVersionValue": {
"base": "<p>The data set whose latest contents will be used as input to the notebook or application.</p>",
"base": "<p>The data set whose latest contents are used as input to the notebook or application.</p>",
"refs": {
"Variable$datasetContentVersionValue": "<p>The value of the variable as a structure that specifies a data set content version.</p>"
}
Expand All @@ -384,14 +384,14 @@
"CreateDatasetRequest$datasetName": "<p>The name of the data set.</p>",
"CreateDatasetResponse$datasetName": "<p>The name of the data set.</p>",
"Dataset$name": "<p>The name of the data set.</p>",
"DatasetContentVersionValue$datasetName": "<p>The name of the data set whose latest contents will be used as input to the notebook or application.</p>",
"DatasetContentVersionValue$datasetName": "<p>The name of the data set whose latest contents are used as input to the notebook or application.</p>",
"DatasetSummary$datasetName": "<p>The name of the data set.</p>",
"DeleteDatasetContentRequest$datasetName": "<p>The name of the data set whose content is deleted.</p>",
"DeleteDatasetRequest$datasetName": "<p>The name of the data set to delete.</p>",
"DescribeDatasetRequest$datasetName": "<p>The name of the data set whose information is retrieved.</p>",
"GetDatasetContentRequest$datasetName": "<p>The name of the data set whose contents are retrieved.</p>",
"ListDatasetContentsRequest$datasetName": "<p>The name of the data set whose contents information you want to list.</p>",
"TriggeringDataset$name": "<p>The name of the data set whose content generation will trigger the new data set content generation.</p>",
"TriggeringDataset$name": "<p>The name of the data set whose content generation triggers the new data set content generation.</p>",
"UpdateDatasetRequest$datasetName": "<p>The name of the data set to update.</p>"
}
},
Expand Down Expand Up @@ -512,9 +512,9 @@
}
},
"DeltaTime": {
"base": "<p>When you create data set contents using message data from a specified time frame, some message data may still be \"in flight\" when processing begins, and so will not arrive in time to be processed. Use this field to make allowances for the \"in flight\" time of your message data, so that data not processed from the previous time frame will be included with the next time frame. Without this, missed message data would be excluded from processing during the next time frame as well, because its timestamp places it within the previous time frame.</p>",
"base": "<p>Used to limit data to that which has arrived since the last execution of the action.</p>",
"refs": {
"QueryFilter$deltaTime": "<p>Used to limit data to that which has arrived since the last execution of the action. When you create data set contents using message data from a specified time frame, some message data may still be \"in flight\" when processing begins, and so will not arrive in time to be processed. Use this field to make allowances for the \"in flight\" time of you message data, so that data not processed from a previous time frame will be included with the next time frame. Without this, missed message data would be excluded from processing during the next time frame as well, because its timestamp places it within the previous time frame.</p>"
"QueryFilter$deltaTime": "<p>Used to limit data to that which has arrived since the last execution of the action.</p>"
}
},
"DescribeChannelRequest": {
Expand Down Expand Up @@ -595,7 +595,7 @@
"EntryName": {
"base": null,
"refs": {
"DatasetContentDeliveryRule$entryName": null,
"DatasetContentDeliveryRule$entryName": "<p>The name of the data set content delivery rules entry.</p>",
"DatasetEntry$entryName": "<p>The name of the data set item.</p>"
}
},
Expand Down Expand Up @@ -664,15 +664,15 @@
}
},
"IotEventsDestinationConfiguration": {
"base": null,
"base": "<p>Configuration information for delivery of data set contents to AWS IoT Events.</p>",
"refs": {
"DatasetContentDeliveryDestination$iotEventsDestinationConfiguration": null
"DatasetContentDeliveryDestination$iotEventsDestinationConfiguration": "<p>Configuration information for delivery of data set contents to AWS IoT Events.</p>"
}
},
"IotEventsInputName": {
"base": null,
"refs": {
"IotEventsDestinationConfiguration$inputName": null
"IotEventsDestinationConfiguration$inputName": "<p>The name of the AWS IoT Events input to which data set contents are delivered.</p>"
}
},
"LambdaActivity": {
Expand Down Expand Up @@ -836,7 +836,7 @@
"Messages": {
"base": null,
"refs": {
"BatchPutMessageRequest$messages": "<p>The list of messages to be sent. Each message has format: '{ \"messageId\": \"string\", \"payload\": \"string\"}'.</p>"
"BatchPutMessageRequest$messages": "<p>The list of messages to be sent. Each message has format: '{ \"messageId\": \"string\", \"payload\": \"string\"}'.</p> <p>Note that the field names of message payloads (data) that you send to AWS IoT Analytics:</p> <ul> <li> <p>Must contain only alphanumeric characters and undescores (_); no other special characters are allowed.</p> </li> <li> <p>Must begin with an alphabetic character or single underscore (_).</p> </li> <li> <p>Cannot contain hyphens (-).</p> </li> <li> <p>In regular expression terms: \"^[A-Za-z_]([A-Za-z0-9]*|[A-Za-z0-9][A-Za-z0-9_]*)$\". </p> </li> <li> <p>Cannot be greater than 255 characters.</p> </li> <li> <p>Are case-insensitive. (Fields named \"foo\" and \"FOO\" in the same payload are considered duplicates.)</p> </li> </ul> <p>For example, {\"temp_01\": 29} or {\"_temp_01\": 29} are valid, but {\"temp-01\": 29}, {\"01_temp\": 29} or {\"__temp_01\": 29} are invalid in message payloads. </p>"
}
},
"NextToken": {
Expand All @@ -857,7 +857,7 @@
"OffsetSeconds": {
"base": null,
"refs": {
"DeltaTime$offsetSeconds": "<p>The number of seconds of estimated \"in flight\" lag time of message data.</p>"
"DeltaTime$offsetSeconds": "<p>The number of seconds of estimated \"in flight\" lag time of message data. When you create data set contents using message data from a specified time frame, some message data may still be \"in flight\" when processing begins, and so will not arrive in time to be processed. Use this field to make allowances for the \"in flight\" time of your message data, so that data not processed from a previous time frame will be included with the next time frame. Without this, missed message data would be excluded from processing during the next time frame as well, because its timestamp places it within the previous time frame.</p>"
}
},
"OutputFileName": {
Expand All @@ -867,7 +867,7 @@
}
},
"OutputFileUriValue": {
"base": "<p>The URI of the location where data set contents are stored, usually the URI of a file in an S3 bucket.</p>",
"base": "<p>The value of the variable as a structure that specifies an output file URI.</p>",
"refs": {
"Variable$outputFileUriValue": "<p>The value of the variable as a structure that specifies an output file URI.</p>"
}
Expand Down Expand Up @@ -997,8 +997,8 @@
"base": null,
"refs": {
"ListTagsForResourceRequest$resourceArn": "<p>The ARN of the resource whose tags you want to list.</p>",
"TagResourceRequest$resourceArn": "<p>The ARN of the resource whose tags will be modified.</p>",
"UntagResourceRequest$resourceArn": "<p>The ARN of the resource whose tags will be removed.</p>"
"TagResourceRequest$resourceArn": "<p>The ARN of the resource whose tags you want to modify.</p>",
"UntagResourceRequest$resourceArn": "<p>The ARN of the resource whose tags you want to remove.</p>"
}
},
"ResourceConfiguration": {
Expand Down Expand Up @@ -1041,7 +1041,7 @@
"ContainerDatasetAction$executionRoleArn": "<p>The ARN of the role which gives permission to the system to access needed resources in order to run the \"containerAction\". This includes, at minimum, permission to retrieve the data set contents which are the input to the containerized application.</p>",
"DeviceRegistryEnrichActivity$roleArn": "<p>The ARN of the role that allows access to the device's registry information.</p>",
"DeviceShadowEnrichActivity$roleArn": "<p>The ARN of the role that allows access to the device's shadow.</p>",
"IotEventsDestinationConfiguration$roleArn": null,
"IotEventsDestinationConfiguration$roleArn": "<p>The ARN of the role which grants AWS IoT Analytics permission to deliver data set contents to an AWS IoT Events input.</p>",
"LoggingOptions$roleArn": "<p>The ARN of the role that grants permission to AWS IoT Analytics to perform logging.</p>"
}
},
Expand Down Expand Up @@ -1103,7 +1103,7 @@
"SqlQueryDatasetAction": {
"base": "<p>The SQL query to modify the message.</p>",
"refs": {
"DatasetAction$queryAction": "<p>An \"SqlQueryDatasetAction\" object that contains the SQL query to modify the message.</p>"
"DatasetAction$queryAction": "<p>An \"SqlQueryDatasetAction\" object that uses an SQL query to automatically create data set contents.</p>"
}
},
"StartPipelineReprocessingRequest": {
Expand Down Expand Up @@ -1145,7 +1145,7 @@
"TagKeyList": {
"base": null,
"refs": {
"UntagResourceRequest$tagKeys": "<p>The keys of those tags which will be removed.</p>"
"UntagResourceRequest$tagKeys": "<p>The keys of those tags which you want to remove.</p>"
}
},
"TagList": {
Expand Down Expand Up @@ -1205,6 +1205,8 @@
"DatastoreSummary$lastUpdateTime": "<p>The last time the data store was updated.</p>",
"EstimatedResourceSize$estimatedOn": "<p>The time when the estimate of the size of the resource was made.</p>",
"GetDatasetContentResponse$timestamp": "<p>The time when the request was made.</p>",
"ListDatasetContentsRequest$scheduledOnOrAfter": "<p>A filter to limit results to those data set contents whose creation is scheduled on or after the given time. See the field <code>triggers.schedule</code> in the CreateDataset request. (timestamp)</p>",
"ListDatasetContentsRequest$scheduledBefore": "<p>A filter to limit results to those data set contents whose creation is scheduled before the given time. See the field <code>triggers.schedule</code> in the CreateDataset request. (timestamp)</p>",
"Pipeline$creationTime": "<p>When the pipeline was created.</p>",
"Pipeline$lastUpdateTime": "<p>The last time the pipeline was updated.</p>",
"PipelineSummary$creationTime": "<p>When the pipeline was created.</p>",
Expand All @@ -1213,9 +1215,9 @@
}
},
"TriggeringDataset": {
"base": "<p>Information about the data set whose content generation will trigger the new data set content generation.</p>",
"base": "<p>Information about the data set whose content generation triggers the new data set content generation.</p>",
"refs": {
"DatasetTrigger$dataset": "<p>The data set whose content creation will trigger the creation of this data set's contents.</p>"
"DatasetTrigger$dataset": "<p>The data set whose content creation triggers the creation of this data set's contents.</p>"
}
},
"UnlimitedRetentionPeriod": {
Expand Down
2 changes: 1 addition & 1 deletion src/data/iotanalytics/2017-11-27/docs-2.json.php

Large diffs are not rendered by default.

0 comments on commit e5f6a67

Please sign in to comment.