Upgrade the aws-config and aws-sdk-s3 crates and use AWS crates that depend on them in tests, specifically
aws_smithy_runtime::client::http::test_util::capture_request to capture a request to read and examine. Make sure the body and headers are set correctly, especially SHA256 headers. Yes, it turns out there was one already, we just add a second? WTF aws-smithy?
Replace the deprecated aws_config::load_from_env() with aws_config::load_defaults() calling it exactly as load_from_env() did.
Remove unnecessary use from the integration tests and run cargo update.
Upgrade the aws-config and aws-sdk-s3 crates and use AWS crates that depend on them in tests, specifically
aws_smithy_runtime::client::http::test_util::capture_request
to capture a request to read and examine. Make sure the body and headers are set correctly, especially SHA256 headers. Yes, it turns out there was one already, we just add a second? WTF aws-smithy?Replace the deprecated
aws_config::load_from_env()
withaws_config::load_defaults()
calling it exactly asload_from_env()
did.Remove unnecessary
use
from the integration tests and runcargo update
.Add
.envrc
; handy to use with direnv.