Update Rust crate rusoto_core to 0.48.0 #20
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.34.0
->0.48.0
Release Notes
rusoto/rusoto (rusoto_core)
v0.48.0
macie
,mobile
, andworklink
services, which have had their DNS records removedhyper-rustls
to0.23
v0.47.0
serde_urlencoded
0.7rustc_version
0.4shlex
1.0hmac
0.4time
-related types inrusoto_signature
withchrono
types, tomatch
rusoto_credential
md5
crate for the RustCryptomd-5
crate, to matchusage of RustCrypto
sha2
crateSync
constraint onByteStream
-related functions.async-trait
,percent-encoding
, andserde
to_string
helpers
cratev0.46.0
rusoto_core::Client
in docsrusoto_mock::MultipleMockRequestDispatcher
base64
0.13bytes
1.0hmac
0.10hyper-rustls
0.22hyper-tls
0.5hyper
0.14tokio
1.0dirs
crate for its replacementdirs-next
pin-project
for the lighter weightpin-project-lite
chrono
'soldtime
featureregex
v0.45.0
subscribe_to_shard
call in Kinesis)rusoto_batch::JobDetail
hmac
0.8 andsha2
0.9Sync
bounds toAsyncRead
andRead
structuresv0.44.0
Time::now()
andOffsetDateTime::now()
deprecation warningstime
crate+
in query stringsMultipleMockRequestDispatcher
to permit mocking multiple requests using the same clientrusoto_sts::WebIdentityProvider::from_k8s_env
always requiringAWS_ROLE_SESSION_NAME
env var which should be optionalrusoto_sts::WebIdentityProvider
region_from_profile()
function to ProfileProviderContent-Encoding
new_with_size()
function to ByteStreamv0.43.0
PrimitiveDateTime
deprecation errorserialize_structs
anddeserialize_structs
WebIdentityProvider
resource_record_sets
methodsDisplay
impl forRusotoError::Unknown
RusotoFuture
and fix docs generation on nightlycredential_process
, agains3.{region}.amazonaws.com
v0.42.0
params for s3
list_objects
methods2017-01-11
rusoto_signature
, a standalone crate for signing HTTP requests.such as an S3 key returned in
list_objects_v2
x-amz-content-sha256
header not being signed: https://github.com/rusoto/rusoto/pull/1545rustls
to be used inrusoto_mock
: https://github.com/rusoto/rusoto/pull/1557v0.41.0
HttpClient::from_builder
1.12.163
to1.12.230
rusoto_events::{CloudWatchEvents,CloudWatchEventsClient}
were renamed torusoto_events::{EventBridge,EventBridgeClient}
#[test]
per behaviorEq
andHash
implementations onRegion
v0.40.0
2018-11-05
serde_json
crate from services where it was not requiredtest_resources
in cargo manifest1.12.156
to1.12.163
should_sha256_sign_payload
argument toSignedRequest::generate_presigned_url
.v0.39.0
Vec<u8>
toBytes
v0.38.0
RusotoError
enum as base error type for all servicesv0.37.0
try!
to?
operator1.12.100
credential_process
support in~/.aws/config
v0.36.0
Option::None
service_crategen
README.mdv0.35.0
From<Result<T, E>> for RusotoFuture<T, E>
implementation for mocking.Luminous
Default
implementation ofRegion
rest-json
protocol published prior to this release . The following service crates were affected.apigateway
,batch
,clouddirectory
,cloudsearchdomain
,cognito-sync
,efs
,eks
,elastictranscoder
,glacier
,greengrass
,guardduty
,iot
,lambda
,lex-models
,lex-runtime
,mq
,polly
,serverlessrepo
,workdocs
,xray
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.