aws-sdk-iotanalytics 1.75.0 → 1.76.0
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/CHANGELOG.md +5 -0
- data/VERSION +1 -1
- data/lib/aws-sdk-iotanalytics/client.rb +10 -10
- data/lib/aws-sdk-iotanalytics/types.rb +15 -15
- data/lib/aws-sdk-iotanalytics.rb +1 -1
- metadata +2 -2
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA256:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: f1d6581a6766573d32315b2168338f709f4cd2200d0a0b417282cb33da114800
|
4
|
+
data.tar.gz: 66a4b0dbd78b1b21c75030a0bdbd16e892762c1aeee7a1007cc3de8fdca22c7d
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 27028676ade43785f635463f01975a3b54b3f23a10fce93d83cedd399bdf2eaf1bd324e59e41bb2ea44d2d87d86e8ef7594cedc4e02a0552805740e7a9e86f64
|
7
|
+
data.tar.gz: 72ee6d8c8f060233064c1d5d594bbf95c7354859b8d68488619c16b49349bd550e94b21a437521b44aafccb4e87fc7297c72da61af7ae71d97bcd8f6d3e74535
|
data/CHANGELOG.md
CHANGED
data/VERSION
CHANGED
@@ -1 +1 @@
|
|
1
|
-
1.
|
1
|
+
1.76.0
|
@@ -453,8 +453,8 @@ module Aws::IoTAnalytics
|
|
453
453
|
# The name of the channel where the messages are sent.
|
454
454
|
#
|
455
455
|
# @option params [required, Array<Types::Message>] :messages
|
456
|
-
# The list of messages to be sent. Each message has the format:
|
457
|
-
# "messageId": "string", "payload": "string"
|
456
|
+
# The list of messages to be sent. Each message has the format: \{
|
457
|
+
# "messageId": "string", "payload": "string"}.
|
458
458
|
#
|
459
459
|
# The field names of message payloads (data) that you send to IoT
|
460
460
|
# Analytics:
|
@@ -474,9 +474,9 @@ module Aws::IoTAnalytics
|
|
474
474
|
# * Are case insensitive. (Fields named foo and FOO in the same payload
|
475
475
|
# are considered duplicates.)
|
476
476
|
#
|
477
|
-
# For example,
|
478
|
-
#
|
479
|
-
#
|
477
|
+
# For example, \{"temp\_01": 29} or \{"\_temp\_01": 29} are valid,
|
478
|
+
# but \{"temp-01": 29}, \{"01\_temp": 29} or \{"\_\_temp\_01": 29}
|
479
|
+
# are invalid in message payloads.
|
480
480
|
#
|
481
481
|
# @return [Types::BatchPutMessageResponse] Returns a {Seahorse::Client::Response response} object which responds to the following methods:
|
482
482
|
#
|
@@ -943,8 +943,8 @@ module Aws::IoTAnalytics
|
|
943
943
|
# a `channel` and a `datastore` activity. Each entry in the list must
|
944
944
|
# contain only one activity. For example:
|
945
945
|
#
|
946
|
-
# `pipelineActivities = [
|
947
|
-
# ...
|
946
|
+
# `pipelineActivities = [ { "channel": { ... } }, { "lambda": { ... } },
|
947
|
+
# ... ]`
|
948
948
|
#
|
949
949
|
# @option params [Array<Types::Tag>] :tags
|
950
950
|
# Metadata which can be used to manage the pipeline.
|
@@ -2263,8 +2263,8 @@ module Aws::IoTAnalytics
|
|
2263
2263
|
# a `channel` and a `datastore` activity. Each entry in the list must
|
2264
2264
|
# contain only one activity. For example:
|
2265
2265
|
#
|
2266
|
-
# `pipelineActivities = [
|
2267
|
-
# ...
|
2266
|
+
# `pipelineActivities = [ { "channel": { ... } }, { "lambda": { ... } },
|
2267
|
+
# ... ]`
|
2268
2268
|
#
|
2269
2269
|
# @return [Struct] Returns an empty {Seahorse::Client::Response response}.
|
2270
2270
|
#
|
@@ -2360,7 +2360,7 @@ module Aws::IoTAnalytics
|
|
2360
2360
|
tracer: tracer
|
2361
2361
|
)
|
2362
2362
|
context[:gem_name] = 'aws-sdk-iotanalytics'
|
2363
|
-
context[:gem_version] = '1.
|
2363
|
+
context[:gem_version] = '1.76.0'
|
2364
2364
|
Seahorse::Client::Request.new(handlers, context)
|
2365
2365
|
end
|
2366
2366
|
|
@@ -67,8 +67,8 @@ module Aws::IoTAnalytics
|
|
67
67
|
# @return [String]
|
68
68
|
#
|
69
69
|
# @!attribute [rw] messages
|
70
|
-
# The list of messages to be sent. Each message has the format:
|
71
|
-
# "messageId": "string", "payload": "string"
|
70
|
+
# The list of messages to be sent. Each message has the format: \{
|
71
|
+
# "messageId": "string", "payload": "string"}.
|
72
72
|
#
|
73
73
|
# The field names of message payloads (data) that you send to IoT
|
74
74
|
# Analytics:
|
@@ -88,9 +88,9 @@ module Aws::IoTAnalytics
|
|
88
88
|
# * Are case insensitive. (Fields named foo and FOO in the same
|
89
89
|
# payload are considered duplicates.)
|
90
90
|
#
|
91
|
-
# For example,
|
92
|
-
#
|
93
|
-
#
|
91
|
+
# For example, \{"temp\_01": 29} or \{"\_temp\_01": 29} are valid,
|
92
|
+
# but \{"temp-01": 29}, \{"01\_temp": 29} or \{"\_\_temp\_01":
|
93
|
+
# 29} are invalid in message payloads.
|
94
94
|
# @return [Array<Types::Message>]
|
95
95
|
#
|
96
96
|
class BatchPutMessageRequest < Struct.new(
|
@@ -643,8 +643,8 @@ module Aws::IoTAnalytics
|
|
643
643
|
# both a `channel` and a `datastore` activity. Each entry in the list
|
644
644
|
# must contain only one activity. For example:
|
645
645
|
#
|
646
|
-
# `pipelineActivities = [
|
647
|
-
#
|
646
|
+
# `pipelineActivities = [ { "channel": { ... } }, { "lambda": { ... }
|
647
|
+
# }, ... ]`
|
648
648
|
# @return [Array<Types::PipelineActivity>]
|
649
649
|
#
|
650
650
|
# @!attribute [rw] tags
|
@@ -2606,19 +2606,19 @@ module Aws::IoTAnalytics
|
|
2606
2606
|
#
|
2607
2607
|
# You can create a unique key with the following options:
|
2608
2608
|
#
|
2609
|
-
# * Use
|
2609
|
+
# * Use `!{iotanalytics:scheduleTime}` to insert the time of a
|
2610
2610
|
# scheduled SQL query run.
|
2611
2611
|
#
|
2612
|
-
# * Use
|
2612
|
+
# * Use `!{iotanalytics:versionId}` to insert a unique hash that
|
2613
2613
|
# identifies a dataset content.
|
2614
2614
|
#
|
2615
|
-
# * Use
|
2616
|
-
#
|
2615
|
+
# * Use `!{iotanalytics:creationTime}` to insert the creation time of
|
2616
|
+
# a dataset content.
|
2617
2617
|
#
|
2618
2618
|
# The following example creates a unique key for a CSV file:
|
2619
|
-
# `dataset/mydataset
|
2619
|
+
# `dataset/mydataset/!{iotanalytics:scheduleTime}/!{iotanalytics:versionId}.csv`
|
2620
2620
|
#
|
2621
|
-
# <note markdown="1"> If you don't use
|
2621
|
+
# <note markdown="1"> If you don't use `!{iotanalytics:versionId}` to specify the key,
|
2622
2622
|
# you might get duplicate keys. For example, you might have two
|
2623
2623
|
# dataset contents with the same `scheduleTime` but different
|
2624
2624
|
# `versionId`s. This means that one dataset content overwrites the
|
@@ -3071,8 +3071,8 @@ module Aws::IoTAnalytics
|
|
3071
3071
|
# both a `channel` and a `datastore` activity. Each entry in the list
|
3072
3072
|
# must contain only one activity. For example:
|
3073
3073
|
#
|
3074
|
-
# `pipelineActivities = [
|
3075
|
-
#
|
3074
|
+
# `pipelineActivities = [ { "channel": { ... } }, { "lambda": { ... }
|
3075
|
+
# }, ... ]`
|
3076
3076
|
# @return [Array<Types::PipelineActivity>]
|
3077
3077
|
#
|
3078
3078
|
class UpdatePipelineRequest < Struct.new(
|
data/lib/aws-sdk-iotanalytics.rb
CHANGED
metadata
CHANGED
@@ -1,14 +1,14 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: aws-sdk-iotanalytics
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 1.
|
4
|
+
version: 1.76.0
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- Amazon Web Services
|
8
8
|
autorequire:
|
9
9
|
bindir: bin
|
10
10
|
cert_chain: []
|
11
|
-
date: 2024-
|
11
|
+
date: 2024-11-06 00:00:00.000000000 Z
|
12
12
|
dependencies:
|
13
13
|
- !ruby/object:Gem::Dependency
|
14
14
|
name: aws-sdk-core
|