aws-sdk-iot 1.137.0 → 1.138.0

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: 5a51d136f0044d776ab3a569c7f2081ff6b70552e960907b44d18aec890bdd8f
4
- data.tar.gz: 0f414843ab2f572753485b47e044661d4211402a6d0ecd901106c14efe106433
3
+ metadata.gz: b8939d8513c840d10e2ab38a7b76cf8fcca1f1bac7d2d0f621052c27bbeccf9f
4
+ data.tar.gz: 9fbd391c7eb92174cf53007c2a66e8cd53466a111c7b0ae903f44d7fe418504c
5
5
  SHA512:
6
- metadata.gz: dd53f1465dfa49e61bd747d9d727edf7470fbd8cf735b09bdb4cfc55fd2494abafaa143147537d0983698c4d4a1aaf6e6b17bf64850eae9359b44d8e2c075625
7
- data.tar.gz: f245069310058019821adaf690c61e2d6157ce633bccb0b1713e216cb718283bac61f9a5025d5159bc7e95254fb55b56fc283c91bc0dbce460a3e1b9d745c809
6
+ metadata.gz: fa92073b3a9597d00215cbe25e3c7fa20526bf4f16bcb58e15f95a37ec132fa165329aeb7df3f120f5840ccbf0f7a13d973888db772b0477640b6e44865c15e5
7
+ data.tar.gz: 7f1f73026cdbad8fe8531e77b617dd9551ce0e8f85f71ad950d9736906ab3b2fc4e24cc1b6982f43ddc89a0a79fd19fb6a61b7a084c6cb857ac1b4460d9989a6
data/CHANGELOG.md CHANGED
@@ -1,6 +1,11 @@
1
1
  Unreleased Changes
2
2
  ------------------
3
3
 
4
+ 1.138.0 (2024-11-06)
5
+ ------------------
6
+
7
+ * Feature - Code Generated Changes, see `./build_tools` or `aws-sdk-core`'s CHANGELOG.md for details.
8
+
4
9
  1.137.0 (2024-10-18)
5
10
  ------------------
6
11
 
data/VERSION CHANGED
@@ -1 +1 @@
1
- 1.137.0
1
+ 1.138.0
@@ -1379,9 +1379,9 @@ module Aws::IoT
1379
1379
  #
1380
1380
  # On Linux and OS X, the command is:
1381
1381
  #
1382
- # `$ ls my-csr-directory/ | xargs -I \{\} aws iot
1382
+ # `$ ls my-csr-directory/ | xargs -I {} aws iot
1383
1383
  # create-certificate-from-csr --certificate-signing-request
1384
- # file://my-csr-directory/\{\}`
1384
+ # file://my-csr-directory/{}`
1385
1385
  #
1386
1386
  # This command lists all of the CSRs in my-csr-directory and pipes each
1387
1387
  # CSR file name to the `aws iot create-certificate-from-csr` Amazon Web
@@ -1391,15 +1391,15 @@ module Aws::IoT
1391
1391
  # You can also run the `aws iot create-certificate-from-csr` part of the
1392
1392
  # command in parallel to speed up the certificate creation process:
1393
1393
  #
1394
- # `$ ls my-csr-directory/ | xargs -P 10 -I \{\} aws iot
1394
+ # `$ ls my-csr-directory/ | xargs -P 10 -I {} aws iot
1395
1395
  # create-certificate-from-csr --certificate-signing-request
1396
- # file://my-csr-directory/\{\} `
1396
+ # file://my-csr-directory/{} `
1397
1397
  #
1398
1398
  # On Windows PowerShell, the command to create certificates for all CSRs
1399
1399
  # in my-csr-directory is:
1400
1400
  #
1401
- # `> ls -Name my-csr-directory | %\{aws iot create-certificate-from-csr
1402
- # --certificate-signing-request file://my-csr-directory/$_\} `
1401
+ # `> ls -Name my-csr-directory | %{aws iot create-certificate-from-csr
1402
+ # --certificate-signing-request file://my-csr-directory/$_} `
1403
1403
  #
1404
1404
  # On a Windows command prompt, the command to create certificates for
1405
1405
  # all CSRs in my-csr-directory is:
@@ -3523,7 +3523,7 @@ module Aws::IoT
3523
3523
  # The attribute payload, which consists of up to three name/value pairs
3524
3524
  # in a JSON document. For example:
3525
3525
  #
3526
- # `\{"attributes":\{"string1":"string2"\}\}`
3526
+ # `{"attributes":{"string1":"string2"}}`
3527
3527
  #
3528
3528
  # @option params [String] :billing_group_name
3529
3529
  # The name of the billing group the thing will be added to.
@@ -15337,7 +15337,7 @@ module Aws::IoT
15337
15337
  # A list of thing attributes, a JSON string containing name-value pairs.
15338
15338
  # For example:
15339
15339
  #
15340
- # `\{"attributes":\{"name1":"value2"\}\}`
15340
+ # `{"attributes":{"name1":"value2"}}`
15341
15341
  #
15342
15342
  # This data is used to add new attributes or update existing attributes.
15343
15343
  #
@@ -15613,7 +15613,7 @@ module Aws::IoT
15613
15613
  tracer: tracer
15614
15614
  )
15615
15615
  context[:gem_name] = 'aws-sdk-iot'
15616
- context[:gem_version] = '1.137.0'
15616
+ context[:gem_version] = '1.138.0'
15617
15617
  Seahorse::Client::Request.new(handlers, context)
15618
15618
  end
15619
15619
 
@@ -692,7 +692,7 @@ module Aws::IoT
692
692
  # A JSON string containing up to three key-value pair in JSON format.
693
693
  # For example:
694
694
  #
695
- # `\{"attributes":\{"string1":"string2"\}\}`
695
+ # `{"attributes":{"string1":"string2"}}`
696
696
  # @return [Hash<String,String>]
697
697
  #
698
698
  # @!attribute [rw] merge
@@ -4196,7 +4196,7 @@ module Aws::IoT
4196
4196
  # The attribute payload, which consists of up to three name/value
4197
4197
  # pairs in a JSON document. For example:
4198
4198
  #
4199
- # `\{"attributes":\{"string1":"string2"\}\}`
4199
+ # `{"attributes":{"string1":"string2"}}`
4200
4200
  # @return [Types::AttributePayload]
4201
4201
  #
4202
4202
  # @!attribute [rw] billing_group_name
@@ -7121,17 +7121,17 @@ module Aws::IoT
7121
7121
  #
7122
7122
  # The `hashKeyValue` and `rangeKeyvalue` fields use a substitution
7123
7123
  # template syntax. These templates provide data at runtime. The syntax
7124
- # is as follows: $\\\{*sql-expression*\\}.
7124
+ # is as follows: $\{*sql-expression*}.
7125
7125
  #
7126
7126
  # You can specify any valid expression in a WHERE or SELECT clause,
7127
7127
  # including JSON properties, comparisons, calculations, and functions.
7128
7128
  # For example, the following field uses the third level of the topic:
7129
7129
  #
7130
- # `"hashKeyValue": "$\{topic(3)\}"`
7130
+ # `"hashKeyValue": "${topic(3)}"`
7131
7131
  #
7132
7132
  # The following field uses the timestamp:
7133
7133
  #
7134
- # `"rangeKeyValue": "$\{timestamp()\}"`
7134
+ # `"rangeKeyValue": "${timestamp()}"`
7135
7135
  #
7136
7136
  # @!attribute [rw] table_name
7137
7137
  # The name of the DynamoDB table.
@@ -7143,7 +7143,7 @@ module Aws::IoT
7143
7143
  #
7144
7144
  # @!attribute [rw] operation
7145
7145
  # The type of operation to be performed. This follows the substitution
7146
- # template, so it can be `$\{operation\}`, but the substitution must
7146
+ # template, so it can be `${operation}`, but the substitution must
7147
7147
  # result in one of the following: `INSERT`, `UPDATE`, or `DELETE`.
7148
7148
  # @return [String]
7149
7149
  #
@@ -7203,8 +7203,8 @@ module Aws::IoT
7203
7203
  # Specifies the DynamoDB table to which the message data will be
7204
7204
  # written. For example:
7205
7205
  #
7206
- # `\{ "dynamoDBv2": \{ "roleArn": "aws:iam:12341251:my-role"
7207
- # "putItem": \{ "tableName": "my-table" \} \} \}`
7206
+ # `{ "dynamoDBv2": { "roleArn": "aws:iam:12341251:my-role" "putItem":
7207
+ # { "tableName": "my-table" } } }`
7208
7208
  #
7209
7209
  # Each attribute in the message payload will be written to a separate
7210
7210
  # column in the DynamoDB database.
@@ -17351,7 +17351,7 @@ module Aws::IoT
17351
17351
  # A list of thing attributes, a JSON string containing name-value
17352
17352
  # pairs. For example:
17353
17353
  #
17354
- # `\{"attributes":\{"name1":"value2"\}\}`
17354
+ # `{"attributes":{"name1":"value2"}}`
17355
17355
  #
17356
17356
  # This data is used to add new attributes or update existing
17357
17357
  # attributes.
data/lib/aws-sdk-iot.rb CHANGED
@@ -54,7 +54,7 @@ module Aws::IoT
54
54
  autoload :EndpointProvider, 'aws-sdk-iot/endpoint_provider'
55
55
  autoload :Endpoints, 'aws-sdk-iot/endpoints'
56
56
 
57
- GEM_VERSION = '1.137.0'
57
+ GEM_VERSION = '1.138.0'
58
58
 
59
59
  end
60
60
 
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: aws-sdk-iot
3
3
  version: !ruby/object:Gem::Version
4
- version: 1.137.0
4
+ version: 1.138.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-10-18 00:00:00.000000000 Z
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