aws-sdk-datasync 1.75.0 → 1.77.0
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/CHANGELOG.md +10 -0
- data/VERSION +1 -1
- data/lib/aws-sdk-datasync/client.rb +45 -27
- data/lib/aws-sdk-datasync/client_api.rb +1 -0
- data/lib/aws-sdk-datasync/types.rb +42 -18
- data/lib/aws-sdk-datasync.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: 358ba4d8506d5901ab7dfdf11b33860c89f80c7b026963c2ea258524e5a2e84c
|
4
|
+
data.tar.gz: 20b38c869da6aa84837520ec59c8a4225073e3ad0cb2cf4393bd757b50ceef97
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: b63f15cd586bc7431f33b1b9b1a57c3248c9f2c39e3cb5b30391ce43cefa91781a34532cded473b22c0052bc0942838af0c3d29222b541f25463f934a592c05c
|
7
|
+
data.tar.gz: 8db57694782d8c2db836bbdc9b87f2408e3520aee4aa3542ecb4aa6769f23ad3ed298d8e4509d1daf7f1ab4672fe4841d8509afd848c038bab12a7154b7752d3
|
data/CHANGELOG.md
CHANGED
@@ -1,6 +1,16 @@
|
|
1
1
|
Unreleased Changes
|
2
2
|
------------------
|
3
3
|
|
4
|
+
1.77.0 (2024-05-13)
|
5
|
+
------------------
|
6
|
+
|
7
|
+
* Feature - Code Generated Changes, see `./build_tools` or `aws-sdk-core`'s CHANGELOG.md for details.
|
8
|
+
|
9
|
+
1.76.0 (2024-05-03)
|
10
|
+
------------------
|
11
|
+
|
12
|
+
* Feature - Updated guidance on using private or self-signed certificate authorities (CAs) with AWS DataSync object storage locations.
|
13
|
+
|
4
14
|
1.75.0 (2024-04-25)
|
5
15
|
------------------
|
6
16
|
|
data/VERSION
CHANGED
@@ -1 +1 @@
|
|
1
|
-
1.
|
1
|
+
1.77.0
|
@@ -301,8 +301,9 @@ module Aws::DataSync
|
|
301
301
|
#
|
302
302
|
# @option options [String] :sdk_ua_app_id
|
303
303
|
# A unique and opaque application ID that is appended to the
|
304
|
-
# User-Agent header as app
|
305
|
-
# maximum length of 50.
|
304
|
+
# User-Agent header as app/sdk_ua_app_id. It should have a
|
305
|
+
# maximum length of 50. This variable is sourced from environment
|
306
|
+
# variable AWS_SDK_UA_APP_ID or the shared config profile attribute sdk_ua_app_id.
|
306
307
|
#
|
307
308
|
# @option options [String] :secret_access_key
|
308
309
|
#
|
@@ -1465,20 +1466,27 @@ module Aws::DataSync
|
|
1465
1466
|
# your resources. We recommend creating a name tag for your location.
|
1466
1467
|
#
|
1467
1468
|
# @option params [String, StringIO, File] :server_certificate
|
1468
|
-
# Specifies a
|
1469
|
-
# object storage
|
1470
|
-
#
|
1471
|
-
#
|
1469
|
+
# Specifies a certificate chain for DataSync to authenticate with your
|
1470
|
+
# object storage system if the system uses a private or self-signed
|
1471
|
+
# certificate authority (CA). You must specify a single `.pem` file with
|
1472
|
+
# a full certificate chain (for example,
|
1473
|
+
# `file:///home/user/.ssh/object_storage_certificates.pem`).
|
1472
1474
|
#
|
1473
|
-
#
|
1475
|
+
# The certificate chain might include:
|
1474
1476
|
#
|
1475
|
-
# *
|
1477
|
+
# * The object storage system's certificate
|
1476
1478
|
#
|
1477
|
-
# *
|
1479
|
+
# * All intermediate certificates (if there are any)
|
1478
1480
|
#
|
1479
|
-
# *
|
1481
|
+
# * The root certificate of the signing CA
|
1480
1482
|
#
|
1481
|
-
#
|
1483
|
+
# You can concatenate your certificates into a `.pem` file (which can be
|
1484
|
+
# up to 32768 bytes before base64 encoding). The following example `cat`
|
1485
|
+
# command creates an `object_storage_certificates.pem` file that
|
1486
|
+
# includes three certificates:
|
1487
|
+
#
|
1488
|
+
# `cat object_server_certificate.pem intermediate_certificate.pem
|
1489
|
+
# ca_root_certificate.pem > object_storage_certificates.pem`
|
1482
1490
|
#
|
1483
1491
|
# To use this parameter, configure `ServerProtocol` to `HTTPS`.
|
1484
1492
|
#
|
@@ -4157,14 +4165,8 @@ module Aws::DataSync
|
|
4157
4165
|
req.send_request(options)
|
4158
4166
|
end
|
4159
4167
|
|
4160
|
-
# Updates some parameters of an existing
|
4161
|
-
#
|
4162
|
-
# self-managed object storage location, see [Creating a location for
|
4163
|
-
# object storage][1].
|
4164
|
-
#
|
4165
|
-
#
|
4166
|
-
#
|
4167
|
-
# [1]: https://docs.aws.amazon.com/datasync/latest/userguide/create-object-location.html
|
4168
|
+
# Updates some parameters of an existing DataSync location for an object
|
4169
|
+
# storage system.
|
4168
4170
|
#
|
4169
4171
|
# @option params [required, String] :location_arn
|
4170
4172
|
# Specifies the ARN of the object storage system location that you're
|
@@ -4197,16 +4199,32 @@ module Aws::DataSync
|
|
4197
4199
|
# can securely connect with your location.
|
4198
4200
|
#
|
4199
4201
|
# @option params [String, StringIO, File] :server_certificate
|
4200
|
-
# Specifies a certificate to authenticate with
|
4201
|
-
#
|
4202
|
-
# must specify a
|
4203
|
-
#
|
4204
|
-
#
|
4202
|
+
# Specifies a certificate chain for DataSync to authenticate with your
|
4203
|
+
# object storage system if the system uses a private or self-signed
|
4204
|
+
# certificate authority (CA). You must specify a single `.pem` file with
|
4205
|
+
# a full certificate chain (for example,
|
4206
|
+
# `file:///home/user/.ssh/object_storage_certificates.pem`).
|
4207
|
+
#
|
4208
|
+
# The certificate chain might include:
|
4209
|
+
#
|
4210
|
+
# * The object storage system's certificate
|
4211
|
+
#
|
4212
|
+
# * All intermediate certificates (if there are any)
|
4213
|
+
#
|
4214
|
+
# * The root certificate of the signing CA
|
4215
|
+
#
|
4216
|
+
# You can concatenate your certificates into a `.pem` file (which can be
|
4217
|
+
# up to 32768 bytes before base64 encoding). The following example `cat`
|
4218
|
+
# command creates an `object_storage_certificates.pem` file that
|
4219
|
+
# includes three certificates:
|
4220
|
+
#
|
4221
|
+
# `cat object_server_certificate.pem intermediate_certificate.pem
|
4222
|
+
# ca_root_certificate.pem > object_storage_certificates.pem`
|
4205
4223
|
#
|
4206
4224
|
# To use this parameter, configure `ServerProtocol` to `HTTPS`.
|
4207
4225
|
#
|
4208
|
-
# Updating
|
4209
|
-
#
|
4226
|
+
# Updating this parameter doesn't interfere with tasks that you have in
|
4227
|
+
# progress.
|
4210
4228
|
#
|
4211
4229
|
# @return [Struct] Returns an empty {Seahorse::Client::Response response}.
|
4212
4230
|
#
|
@@ -4635,7 +4653,7 @@ module Aws::DataSync
|
|
4635
4653
|
params: params,
|
4636
4654
|
config: config)
|
4637
4655
|
context[:gem_name] = 'aws-sdk-datasync'
|
4638
|
-
context[:gem_version] = '1.
|
4656
|
+
context[:gem_version] = '1.77.0'
|
4639
4657
|
Seahorse::Client::Request.new(handlers, context)
|
4640
4658
|
end
|
4641
4659
|
|
@@ -1365,6 +1365,7 @@ module Aws::DataSync
|
|
1365
1365
|
"endpointPrefix" => "datasync",
|
1366
1366
|
"jsonVersion" => "1.1",
|
1367
1367
|
"protocol" => "json",
|
1368
|
+
"protocols" => ["json"],
|
1368
1369
|
"serviceAbbreviation" => "DataSync",
|
1369
1370
|
"serviceFullName" => "AWS DataSync",
|
1370
1371
|
"serviceId" => "DataSync",
|
@@ -983,20 +983,27 @@ module Aws::DataSync
|
|
983
983
|
# @return [Array<Types::TagListEntry>]
|
984
984
|
#
|
985
985
|
# @!attribute [rw] server_certificate
|
986
|
-
# Specifies a
|
987
|
-
# object storage
|
988
|
-
#
|
989
|
-
#
|
986
|
+
# Specifies a certificate chain for DataSync to authenticate with your
|
987
|
+
# object storage system if the system uses a private or self-signed
|
988
|
+
# certificate authority (CA). You must specify a single `.pem` file
|
989
|
+
# with a full certificate chain (for example,
|
990
|
+
# `file:///home/user/.ssh/object_storage_certificates.pem`).
|
990
991
|
#
|
991
|
-
#
|
992
|
+
# The certificate chain might include:
|
992
993
|
#
|
993
|
-
# *
|
994
|
+
# * The object storage system's certificate
|
994
995
|
#
|
995
|
-
# *
|
996
|
+
# * All intermediate certificates (if there are any)
|
996
997
|
#
|
997
|
-
# *
|
998
|
+
# * The root certificate of the signing CA
|
998
999
|
#
|
999
|
-
#
|
1000
|
+
# You can concatenate your certificates into a `.pem` file (which can
|
1001
|
+
# be up to 32768 bytes before base64 encoding). The following example
|
1002
|
+
# `cat` command creates an `object_storage_certificates.pem` file that
|
1003
|
+
# includes three certificates:
|
1004
|
+
#
|
1005
|
+
# `cat object_server_certificate.pem intermediate_certificate.pem
|
1006
|
+
# ca_root_certificate.pem > object_storage_certificates.pem`
|
1000
1007
|
#
|
1001
1008
|
# To use this parameter, configure `ServerProtocol` to `HTTPS`.
|
1002
1009
|
# @return [String]
|
@@ -2139,8 +2146,9 @@ module Aws::DataSync
|
|
2139
2146
|
# @return [Time]
|
2140
2147
|
#
|
2141
2148
|
# @!attribute [rw] server_certificate
|
2142
|
-
# The
|
2143
|
-
#
|
2149
|
+
# The certificate chain for DataSync to authenticate with your object
|
2150
|
+
# storage system if the system uses a private or self-signed
|
2151
|
+
# certificate authority (CA).
|
2144
2152
|
# @return [String]
|
2145
2153
|
#
|
2146
2154
|
# @see http://docs.aws.amazon.com/goto/WebAPI/datasync-2018-11-09/DescribeLocationObjectStorageResponse AWS API Documentation
|
@@ -5516,7 +5524,7 @@ module Aws::DataSync
|
|
5516
5524
|
# Specifies whether to enable or disable your task schedule. Your
|
5517
5525
|
# schedule is enabled by default, but there can be situations where
|
5518
5526
|
# you need to disable it. For example, you might need to pause a
|
5519
|
-
# recurring transfer
|
5527
|
+
# recurring transfer to fix an issue with your task or perform
|
5520
5528
|
# maintenance on your storage system.
|
5521
5529
|
#
|
5522
5530
|
# DataSync might disable your schedule automatically if your task
|
@@ -5938,15 +5946,31 @@ module Aws::DataSync
|
|
5938
5946
|
# @return [Array<String>]
|
5939
5947
|
#
|
5940
5948
|
# @!attribute [rw] server_certificate
|
5941
|
-
# Specifies a certificate to authenticate with
|
5942
|
-
# system
|
5943
|
-
# (CA). You must specify a
|
5944
|
-
#
|
5945
|
-
#
|
5949
|
+
# Specifies a certificate chain for DataSync to authenticate with your
|
5950
|
+
# object storage system if the system uses a private or self-signed
|
5951
|
+
# certificate authority (CA). You must specify a single `.pem` file
|
5952
|
+
# with a full certificate chain (for example,
|
5953
|
+
# `file:///home/user/.ssh/object_storage_certificates.pem`).
|
5954
|
+
#
|
5955
|
+
# The certificate chain might include:
|
5956
|
+
#
|
5957
|
+
# * The object storage system's certificate
|
5958
|
+
#
|
5959
|
+
# * All intermediate certificates (if there are any)
|
5960
|
+
#
|
5961
|
+
# * The root certificate of the signing CA
|
5962
|
+
#
|
5963
|
+
# You can concatenate your certificates into a `.pem` file (which can
|
5964
|
+
# be up to 32768 bytes before base64 encoding). The following example
|
5965
|
+
# `cat` command creates an `object_storage_certificates.pem` file that
|
5966
|
+
# includes three certificates:
|
5967
|
+
#
|
5968
|
+
# `cat object_server_certificate.pem intermediate_certificate.pem
|
5969
|
+
# ca_root_certificate.pem > object_storage_certificates.pem`
|
5946
5970
|
#
|
5947
5971
|
# To use this parameter, configure `ServerProtocol` to `HTTPS`.
|
5948
5972
|
#
|
5949
|
-
# Updating
|
5973
|
+
# Updating this parameter doesn't interfere with tasks that you have
|
5950
5974
|
# in progress.
|
5951
5975
|
# @return [String]
|
5952
5976
|
#
|
data/lib/aws-sdk-datasync.rb
CHANGED
metadata
CHANGED
@@ -1,14 +1,14 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: aws-sdk-datasync
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 1.
|
4
|
+
version: 1.77.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-05-13 00:00:00.000000000 Z
|
12
12
|
dependencies:
|
13
13
|
- !ruby/object:Gem::Dependency
|
14
14
|
name: aws-sdk-core
|