search

Nugine / s3s

S3 Service Adapter
Apache License 2.0
133 stars 33 forks source link

build(deps): bump the dependencies group with 5 updates #110

Closed dependabot[bot] closed 9 months ago

dependabot[bot] commented 9 months ago

Updates the requirements on aws-sdk-s3, aws-smithy-http, aws-smithy-types, aws-smithy-types-convert and hyper to permit the latest version. Updates aws-sdk-s3 to 1.1.0

Changelog

Sourced from aws-sdk-s3's changelog.

November 27th, 2023

New this release:

Service Features:

  • aws-sdk-accessanalyzer (1.2.0): IAM Access Analyzer now continuously monitors IAM roles and users in your AWS account or organization to generate findings for unused access. Additionally, IAM Access Analyzer now provides custom policy checks to validate that IAM policies adhere to your security standards ahead of deployments.
  • aws-sdk-amp (1.2.0): This release adds support for the Amazon Managed Service for Prometheus collector, a fully managed, agentless Prometheus metrics scraping capability.
  • aws-sdk-bcmdataexports (1.0.0): Users can create, read, update, delete Exports of billing and cost management data. Users can get details of Export Executions and details of Tables for exporting. Tagging support is provided for Exports
  • aws-sdk-cloudtrail (1.2.0): CloudTrail Lake now supports federating event data stores. giving users the ability to run queries against their event data using Amazon Athena.
  • aws-sdk-cloudwatchlogs (1.2.0): Added APIs to Create, Update, Get, List and Delete LogAnomalyDetectors and List and Update Anomalies in Detector. Added LogGroupClass attribute for LogGroups to classify loggroup as Standard loggroup with all capabilities or InfrequentAccess loggroup with limited capabilities.
  • aws-sdk-codestarconnections (1.2.0): This release adds support for the CloudFormation Git sync feature. Git sync enables updating a CloudFormation stack from a template stored in a Git repository.
  • aws-sdk-computeoptimizer (1.2.0): This release enables AWS Compute Optimizer to analyze and generate recommendations with customization and discounts preferences.
  • aws-sdk-config (1.2.0): Support Periodic Recording for Configuration Recorder
  • aws-sdk-controltower (1.2.0): Add APIs to create and manage a landing zone.
  • aws-sdk-costoptimizationhub (1.0.0): This release launches Cost Optimization Hub, a new AWS Billing and Cost Management feature that helps you consolidate and prioritize cost optimization recommendations across your AWS Organizations member accounts and AWS Regions, so that you can get the most out of your AWS spend.
  • aws-sdk-detective (1.2.0): Added new APIs in Detective to support resource investigations
  • aws-sdk-ecs (1.2.0): Adds a new 'type' property to the Setting structure. Adds a new AccountSetting - guardDutyActivate for ECS.
  • aws-sdk-efs (1.2.0): Adding support for EFS Archive lifecycle configuration.
  • aws-sdk-eks (1.2.0): This release adds support for EKS Pod Identity feature. EKS Pod Identity makes it easy for customers to obtain IAM permissions for the applications running in their EKS clusters.
  • aws-sdk-eksauth (1.0.0): This release adds support for EKS Pod Identity feature. EKS Pod Identity makes it easy for customers to obtain IAM permissions for their applications running in the EKS clusters.
  • aws-sdk-elasticloadbalancingv2 (1.2.0): This release enables both mutual authentication (mTLS), and Automatic Target Weights (ATW) for Application Load Balancers.
  • aws-sdk-freetier (1.0.0): This is the initial SDK release for the AWS Free Tier GetFreeTierUsage API
  • aws-sdk-fsx (1.2.0): Added support for FSx for ONTAP scale-out file systems and FlexGroup volumes. Added the HAPairs field and ThroughputCapacityPerHAPair for filesystem. Added AggregateConfiguration (containing Aggregates and ConstituentsPerAggregate) and SizeInBytes for volume.
  • aws-sdk-guardduty (1.2.0): Add support for Runtime Monitoring for ECS and ECS-EC2.
  • aws-sdk-iotfleetwise (1.2.0): AWS IoT FleetWise introduces new APIs for vision system data, such as data collected from cameras, radars, and lidars. You can now model and decode complex data types.
  • aws-sdk-lakeformation (1.2.0): This release adds four new APIs "DescribeLakeFormationIdentityCenterConfiguration", "CreateLakeFormationIdentityCenterConfiguration", "DescribeLakeFormationIdentityCenterConfiguration", and "DeleteLakeFormationIdentityCenterConfiguration", and also updates the corresponding documentation.
  • aws-sdk-lexmodelsv2 (1.2.0): This release introduces new generative AI features in AWS Lex: Assisted Slot Resolution, Descriptive Bot Building, and Sample Utterance Generation. These features leverage large language models available through Amazon Bedrock to improve the bot builder and customer experiences.
  • aws-sdk-lexruntimev2 (1.2.0): This release introduces support for interpretationSource in the runtime service response.
  • aws-sdk-managedblockchain (1.2.0): Add optional NetworkType property to Accessor APIs
  • aws-sdk-personalize (1.2.0): Enables metadata in recommendations, recommendations with themes, and next best action recommendations
  • aws-sdk-personalizeevents (1.2.0): This release enables PutActions and PutActionInteractions
  • aws-sdk-personalizeruntime (1.2.0): Enables metadata in recommendations and next best action recommendations
  • aws-sdk-quicksight (1.2.0): This release launches new APIs for trusted identity propagation setup and supports creating datasources using trusted identity propagation as authentication method for QuickSight accounts configured with IAM Identity Center.
  • aws-sdk-redshift (1.2.0): This release adds support for multi-data warehouse writes through data sharing.
  • aws-sdk-repostspace (1.0.0): Initial release of AWS re:Post Private
  • aws-sdk-s3 (1.2.0): Adding new params - Key and Prefix, to S3 API operations for supporting S3 Access Grants. Note - These updates will not change any of the existing S3 API functionality.
  • aws-sdk-s3control (1.2.0): Introduce Amazon S3 Access Grants, a new S3 access control feature that maps identities in directories such as Active Directory, or AWS Identity and Access Management (IAM) Principals, to datasets in S3.
  • aws-sdk-secretsmanager (1.2.0): AWS Secrets Manager has released the BatchGetSecretValue API, which allows customers to fetch up to 20 Secrets with a single request using a list of secret names or filters.
  • aws-sdk-securityhub (1.2.0): Adds and updates APIs to support customizable security controls. This feature allows Security Hub customers to provide custom parameters for security controls. With this release, findings for controls that support custom parameters will include the parameters used to generate the findings.
  • aws-sdk-sfn (1.2.0): Adds new TestState operation which accepts the definition of a single state and executes it. You can test a state without creating a state machine or updating an existing state machine.
  • aws-sdk-transcribe (1.2.0): This release adds support for transcriptions from audio sources in 64 new languages and introduces generative call summarization in Transcribe Call Analytics (Post call)
  • aws-sdk-workspaces (1.2.0): The release introduces Multi-Region Resilience one-way data replication that allows you to replicate data from your primary WorkSpace to a standby WorkSpace in another AWS Region. DescribeWorkspaces now returns the status of data replication.
  • aws-sdk-workspacesthinclient (1.0.0): Initial release of Amazon WorkSpaces Thin Client

Crate Versions

... (truncated)

Commits


Updates aws-smithy-http to 0.60.0

Changelog

Sourced from aws-smithy-http's changelog.

November 21st, 2023

Internal changes only with this release

November 17th, 2023

Breaking Changes:

  • :warning::tada: (client, smithy-rs#3202) Add configurable stalled-stream protection for downloads.

    When making HTTP calls, it's possible for a connection to 'stall out' and emit no more data due to server-side issues. In the event this happens, it's desirable for the stream to error out as quickly as possible. While timeouts can protect you from this issue, they aren't adaptive to the amount of data being sent and so must be configured specifically for each use case. When enabled, stalled-stream protection will ensure that bad streams error out quickly, regardless of the amount of data being downloaded.

    Protection is enabled by default for all clients but can be configured or disabled. See this discussion for more details.

  • :warning: (client, smithy-rs#3222) Types/functions that were deprecated in previous releases were removed. Unfortunately, some of these deprecations were ignored by the Rust compiler (we found out later that #[deprecated] on pub use doesn't work). See the deprecations removal list for more details.

  • :warning: (all, smithy-rs#3236) Conversions for HTTP request in aws-smithy-runtime-api are now feature gated behind the http-02x feature

New this release:

  • :tada: (all, smithy-rs#3183, @​HakanVardarr) Add Display impl for DateTime.
  • :bug: (client, smithy-rs#3229, aws-sdk-rust#960) Prevent multiplication overflow in backoff computation
  • (client, smithy-rs#3226) Types/functions that were previously #[doc(hidden)] in aws-smithy-async, aws-smithy-runtime-api, aws-smithy-runtime, aws-smithy-types, and the SDK crates are now visible. For those that are not intended to be used directly, they are called out in their docs as such.

Contributors Thank you for your contributions! ❤

November 16th, 2023

Breaking Changes:

  • :warning: (client, smithy-rs#3205) SignableRequest::apply_to_request in aws_sigv4 has been renamed apply_to_request_http0x

November 15th, 2023

Breaking Changes:

  • :warning: (all, smithy-rs#3138, smithy-rs#3148) Upgrade guidance for HTTP Request/Response changes. HTTP request types moved, and a new HTTP response type was added.
  • :warning: (all, smithy-rs#3139) Message, Header, HeaderValue, and StrBytes have been moved to aws-smithy-types from aws-smithy-eventstream. Message::read_from and Message::write_to remain in aws-smithy-eventstream but they are converted to free functions with the names read_message_from and write_message_to respectively.
  • :warning: (client, smithy-rs#3100, smithy-rs#3114) An operation output that supports receiving events from stream now provides a new-type wrapping aws_smithy_http::event_stream::receiver::Receiver. The new-type supports the .recv() method whose signature is the same as aws_smithy_http::event_stream::receiver::Receiver::recv.
  • :warning: (all, smithy-rs#3151) Clients now require a BehaviorVersion to be provided. For must customers, latest is the best choice. This will be enabled automatically if you enable the behavior-version-latest cargo feature on aws-config or on an SDK crate. For customers that wish to pin to a specific behavior major version, it can be set in aws-config or when constructing the service client.

... (truncated)

Commits


Updates aws-smithy-types to 1.0.1

Changelog

Sourced from aws-smithy-types's changelog.

November 21st, 2023

Internal changes only with this release

November 17th, 2023

Breaking Changes:

  • :warning::tada: (client, smithy-rs#3202) Add configurable stalled-stream protection for downloads.

    When making HTTP calls, it's possible for a connection to 'stall out' and emit no more data due to server-side issues. In the event this happens, it's desirable for the stream to error out as quickly as possible. While timeouts can protect you from this issue, they aren't adaptive to the amount of data being sent and so must be configured specifically for each use case. When enabled, stalled-stream protection will ensure that bad streams error out quickly, regardless of the amount of data being downloaded.

    Protection is enabled by default for all clients but can be configured or disabled. See this discussion for more details.

  • :warning: (client, smithy-rs#3222) Types/functions that were deprecated in previous releases were removed. Unfortunately, some of these deprecations were ignored by the Rust compiler (we found out later that #[deprecated] on pub use doesn't work). See the deprecations removal list for more details.

  • :warning: (all, smithy-rs#3236) Conversions for HTTP request in aws-smithy-runtime-api are now feature gated behind the http-02x feature

New this release:

  • :tada: (all, smithy-rs#3183, @​HakanVardarr) Add Display impl for DateTime.
  • :bug: (client, smithy-rs#3229, aws-sdk-rust#960) Prevent multiplication overflow in backoff computation
  • (client, smithy-rs#3226) Types/functions that were previously #[doc(hidden)] in aws-smithy-async, aws-smithy-runtime-api, aws-smithy-runtime, aws-smithy-types, and the SDK crates are now visible. For those that are not intended to be used directly, they are called out in their docs as such.

Contributors Thank you for your contributions! ❤

November 16th, 2023

Breaking Changes:

  • :warning: (client, smithy-rs#3205) SignableRequest::apply_to_request in aws_sigv4 has been renamed apply_to_request_http0x

November 15th, 2023

Breaking Changes:

  • :warning: (all, smithy-rs#3138, smithy-rs#3148) Upgrade guidance for HTTP Request/Response changes. HTTP request types moved, and a new HTTP response type was added.
  • :warning: (all, smithy-rs#3139) Message, Header, HeaderValue, and StrBytes have been moved to aws-smithy-types from aws-smithy-eventstream. Message::read_from and Message::write_to remain in aws-smithy-eventstream but they are converted to free functions with the names read_message_from and write_message_to respectively.
  • :warning: (client, smithy-rs#3100, smithy-rs#3114) An operation output that supports receiving events from stream now provides a new-type wrapping aws_smithy_http::event_stream::receiver::Receiver. The new-type supports the .recv() method whose signature is the same as aws_smithy_http::event_stream::receiver::Receiver::recv.
  • :warning: (all, smithy-rs#3151) Clients now require a BehaviorVersion to be provided. For must customers, latest is the best choice. This will be enabled automatically if you enable the behavior-version-latest cargo feature on aws-config or on an SDK crate. For customers that wish to pin to a specific behavior major version, it can be set in aws-config or when constructing the service client.

... (truncated)

Commits


Updates aws-smithy-types-convert to 0.60.0

Changelog

Sourced from aws-smithy-types-convert's changelog.

November 21st, 2023

Internal changes only with this release

November 17th, 2023

Breaking Changes:

  • :warning::tada: (client, smithy-rs#3202) Add configurable stalled-stream protection for downloads.

    When making HTTP calls, it's possible for a connection to 'stall out' and emit no more data due to server-side issues. In the event this happens, it's desirable for the stream to error out as quickly as possible. While timeouts can protect you from this issue, they aren't adaptive to the amount of data being sent and so must be configured specifically for each use case. When enabled, stalled-stream protection will ensure that bad streams error out quickly, regardless of the amount of data being downloaded.

    Protection is enabled by default for all clients but can be configured or disabled. See this discussion for more details.

  • :warning: (client, smithy-rs#3222) Types/functions that were deprecated in previous releases were removed. Unfortunately, some of these deprecations were ignored by the Rust compiler (we found out later that #[deprecated] on pub use doesn't work). See the deprecations removal list for more details.

  • :warning: (all, smithy-rs#3236) Conversions for HTTP request in aws-smithy-runtime-api are now feature gated behind the http-02x feature

New this release:

  • :tada: (all, smithy-rs#3183, @​HakanVardarr) Add Display impl for DateTime.
  • :bug: (client, smithy-rs#3229, aws-sdk-rust#960) Prevent multiplication overflow in backoff computation
  • (client, smithy-rs#3226) Types/functions that were previously #[doc(hidden)] in aws-smithy-async, aws-smithy-runtime-api, aws-smithy-runtime, aws-smithy-types, and the SDK crates are now visible. For those that are not intended to be used directly, they are called out in their docs as such.

Contributors Thank you for your contributions! ❤

November 16th, 2023

Breaking Changes:

  • :warning: (client, smithy-rs#3205) SignableRequest::apply_to_request in aws_sigv4 has been renamed apply_to_request_http0x

November 15th, 2023

Breaking Changes:

  • :warning: (all, smithy-rs#3138, smithy-rs#3148) Upgrade guidance for HTTP Request/Response changes. HTTP request types moved, and a new HTTP response type was added.
  • :warning: (all, smithy-rs#3139) Message, Header, HeaderValue, and StrBytes have been moved to aws-smithy-types from aws-smithy-eventstream. Message::read_from and Message::write_to remain in aws-smithy-eventstream but they are converted to free functions with the names read_message_from and write_message_to respectively.
  • :warning: (client, smithy-rs#3100, smithy-rs#3114) An operation output that supports receiving events from stream now provides a new-type wrapping aws_smithy_http::event_stream::receiver::Receiver. The new-type supports the .recv() method whose signature is the same as aws_smithy_http::event_stream::receiver::Receiver::recv.
  • :warning: (all, smithy-rs#3151) Clients now require a BehaviorVersion to be provided. For must customers, latest is the best choice. This will be enabled automatically if you enable the behavior-version-latest cargo feature on aws-config or on an SDK crate. For customers that wish to pin to a specific behavior major version, it can be set in aws-config or when constructing the service client.

... (truncated)

Commits


Updates hyper to 1.0.1

Release notes

Sourced from hyper's releases.

v1.0.1

This release "fixes" or adds a few things that should have been in 1.0.0, but were forgotten. Thus, it includes additions that would normally be a semver-minor release, but because it is so close to 1.0.0, it is released as a patch version.

Bug Fixes

Features

  • rt: Make ReadBuf::new public (7161f562)

Breaking Changes

  • Pin is #[fundamental], so providing a Read/Write impl for it theoretically conflicts with existing user Read/Write for Pin impls. However, those impls probably don't exist yet. (dd6d81ca)

New Contributors

Changelog

Sourced from hyper's changelog.

v1.0.1 (2023-11-16)

This release "fixes" or adds a few things that should have been in 1.0.0, but were forgotten. Thus, it includes additions that would normally be a semver-minor release, but because it is so close to 1.0.0, it is released as a patch version.

Bug Fixes

Features

  • rt: Make ReadBuf::new public (7161f562)

Breaking Changes

  • Pin is #[fundamental], so providing a Read/Write impl for it theoretically conflicts with existing user Read/Write for Pin impls. However, those impls probably don't exist yet. (dd6d81ca)

v1.0.0 (2023-11-15)

Bug Fixes

Features

  • client: allow !Send IO with HTTP/1 client (#3371) (cf87eda8, closes #3363)
  • error:
  • ext:
    • make ReasonPhrase::from_static a const fn (d4a61e3d)
    • remove ReasonPhrase::from_bytes_unchecked() method (4021c57b)
  • lib:

... (truncated)

Commits
  • 2954280 v1.0.1
  • 7161f56 feat(rt): Make ReadBuf::new public
  • b855475 refactor(proto): use derive macro to implement Default for KA
  • 823d2cb refactor(lib): remove redundant field name
  • 33e1cbe refactor(lib): remove unneeded return
  • b7e8f88 refactor(lib): remove unused cfg condition
  • dd6d81c fix(rt): implement Read/Write for Pin<P> (#3413)
  • a475ada docs(examples): update dependencies section
  • f1bb2aa chore(ci): add minimal versions checking
  • 931aee7 chore(dependencies): relax minimum tokio version to 1
  • 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 show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore ` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore ` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions
dependabot[bot] commented 9 months ago

Looks like these dependencies are updatable in another way, so this is no longer needed.