chore(deps): bump aws-sdk-sqs from 0.8.0 to 0.9.0

[dependabot]

Bumps aws-sdk-sqs from 0.8.0 to 0.9.0.

Release notes

Sourced from aws-sdk-sqs's releases.

0.9.0 (March 17, 2022)

Breaking Changes:

• ⚠ (aws-sdk-rust#406) aws_types::config::Config has been renamed to aws_types::sdk_config::SdkConfig. This is to better differentiate it from service-specific configs like aws_sdk_s3::Config. If you were creating shared configs with aws_config::load_from_env(), then you don't have to do anything. If you were directly referring to a shared config, update your use statements and struct names.

  Before:

  use aws_types::config::Config;
  fn main() {
  let config = Config::builder()
  // config builder methods...
  .build()
  .await;
  }

  After:

  // We re-export this type from the root module so it's easier to reference
  use aws_types::SdkConfig;
  fn main() {
  let config = SdkConfig::builder()
  // config builder methods...
  .build()
  .await;
  }

• ⚠ (smithy-rs#724) Timeout configuration has been refactored a bit. If you were setting timeouts through environment variables or an AWS profile, then you shouldn't need to change anything. Take note, however, that we don't currently support HTTP connect, read, write, or TLS negotiation timeouts. If you try to set any of those timeouts in your profile or environment, we'll log a warning explaining that those timeouts don't currently do anything.

  If you were using timeouts programmatically, you'll need to update your code. In previous versions, timeout configuration was stored in a single TimeoutConfig struct. In this new version, timeouts have been broken up into several different config structs that are then collected in a timeout::Config struct. As an example, to get the API per-attempt timeout in previous versions you would access it with <your TimeoutConfig>.api_call_attempt_timeout() and in this new version you would access it with <your timeout::Config>.api.call_attempt_timeout(). We also made some unimplemented timeouts inaccessible in order to avoid giving users the impression that setting them had an effect. We plan to re-introduce them once they're made functional in a future update.

New this release:

• 🎉 (aws-sdk-rust#475, aws-sdk-rust#473) Enable presigning for S3 operations UploadPart and DeleteObject

Changelog

Sourced from aws-sdk-sqs's changelog.

0.9.0 (March 17, 2022)

Breaking Changes:

• ⚠ (aws-sdk-rust#406) aws_types::config::Config has been renamed to aws_types::sdk_config::SdkConfig. This is to better differentiate it from service-specific configs like aws_sdk_s3::Config. If you were creating shared configs with aws_config::load_from_env(), then you don't have to do anything. If you were directly referring to a shared config, update your use statements and struct names.

  Before:

  use aws_types::config::Config;
  fn main() {
  let config = Config::builder()
  // config builder methods...
  .build()
  .await;
  }

  After:

  // We re-export this type from the root module so it's easier to reference
  use aws_types::SdkConfig;
  fn main() {
  let config = SdkConfig::builder()
  // config builder methods...
  .build()
  .await;
  }

• ⚠ (smithy-rs#724) Timeout configuration has been refactored a bit. If you were setting timeouts through environment variables or an AWS profile, then you shouldn't need to change anything. Take note, however, that we don't currently support HTTP connect, read, write, or TLS negotiation timeouts. If you try to set any of those timeouts in your profile or environment, we'll log a warning explaining that those timeouts don't currently do anything.

  If you were using timeouts programmatically, you'll need to update your code. In previous versions, timeout configuration was stored in a single TimeoutConfig struct. In this new version, timeouts have been broken up into several different config structs that are then collected in a timeout::Config struct. As an example, to get the API per-attempt timeout in previous versions you would access it with <your TimeoutConfig>.api_call_attempt_timeout() and in this new version you would access it with <your timeout::Config>.api.call_attempt_timeout(). We also made some unimplemented timeouts inaccessible in order to avoid giving users the impression that setting them had an effect. We plan to re-introduce them once they're made functional in a future update.

New this release:

• 🎉 (aws-sdk-rust#475, aws-sdk-rust#473) Enable presigning for S3 operations UploadPart and DeleteObject

Commits

• f4a1458 [autosync] Prepare for release (#1261)
• 6e68bd9 [autosync] Make server operation input and output wrappers pub(crate) (#1253)
• 35373cb [autosync] Add default list of http versions to request property bag (#1258)
• 75dfe2b [autosync] Make generateDeserializePayloadFn not take in an operation shape...
• d53c304 [autosync] Fix docs for aws_smithy_types::Number converters (#1252)
• 4affc2a [autosync] Timeouts refactor (#1246)
• 7c26cc0 [autosync] Try to play a little with benchmark params to increase reliability...
• a38a6e9 [autosync] Revamp error system (#1233)
• 9134e4c [autosync] Rename aws_types::config::Config to sdk_config::SdkConfig (#1241)
• c2f48d7 [autosync] Update README.md (#1245)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)