Tags: Niedzwiedzw/rust-s3
Tags
0.31.0 (durch#268) * Add custom_queries to command PresignGet (durch#262) * fmt * s3: Bump hmac to 0.12, sha2 to 0.10 and minidom to 0.14 (durch#265) * cargo: Bump `hmac` to `0.12 * cargo: Update `sha2` to `0.10` * cargo: bump `minidom` to `0.14` * removed use of `NewMac` trait Co-authored-by: Drazen Urch <[email protected]> * Fix merge * awscreds 0.29.0 * aws-region 0.24 * awsregion 0.24.1 * awscreds 0.29.1 * s3 0.31.0 Co-authored-by: Incomplete <[email protected]> Co-authored-by: Luca Quartesan <[email protected]>
s3 0.29.0 (durch#253) * cargo: Move `tokio-stream` create behind the `with-tokio` feature (durch#248) `tokio-stream` has a dependency on `tokio` and is only used within the `request` module, which depends on the `with-tokio` feature. As such, in order to completely prevent `tokio` from appearing in the crate graph, this crate must be marked optional and enabled when `with-tokio` is requested, omitted otherwise. Also includes two drive-by typo-fixes in the features section of the readme. * Fixup durch#248 * Migrate from `chrono` to `time` to solve RUSTSEC-2020-0159 (durch#250) `chrono` still hasn't found a solution to [RUSTSEC-2020-0159] whereas `time` already solved its vulnerability to [RUSTSEC-2020-0071] by hiding the affected functionality behind a cfg flag (not to be confused with a `feature`, such `cfg`s can only be enabled through `RUSTFLAGS`). At the same time `chrono` is a superset of `time` even though this crate hardly uses any functionality of it: only UTC time is needed which does not suffer from aforementioned local time vulnerabilities. [RUSTSEC-2020-0071]: https://rustsec.org/advisories/RUSTSEC-2020-0071 [RUSTSEC-2020-0159]: https://rustsec.org/advisories/RUSTSEC-2020-0159 Co-authored-by: Drazen Urch <[email protected]> * Update Makefile * Closes durch#245 * Bump aws-region * s3 0.29.0 Co-authored-by: Marijn Suijten <[email protected]>
0.28.0 (durch#238) * aws-creds: default to a 30-second request timeout No (infinite) timeout is a bad default. * aws-creds: return the previous timeout when overriding The value is global, so it's not always possible to restore a previous setting value, but it's better than nothing. * Simplify instance detection * Add ap-east-1 region (durch#235) Co-authored-by: Juraj Sadel <[email protected]> * Fix crates.io badge, update links and various formatting (durch#219) * Make all fail-on-err variations run the same check (durch#233) * Make attohttpc optional for credentials (durch#231) * Make attohttpc optional for credentials * Enabling tls implies enabling http * Use async write for tokio,async-std (durch#230) * Fix tokio async doctest * Add support for the older ListObjects API (durch#229) Google Cloud Storage doesn't support the newer ListObjectsV2 call. * If file is smaller than one chunk, don't initiate multi-part upload (durch#228) There already was a special case in put_object_stream() for a small files, where the multi-part upload was aborted if the input turned out to be small enough to fit in one chunk. But we can do better than that, and not initiate the multi-part upload in the first place, avoiding two round trips to S3 (one to initiate, and another to abort the multi-part upload). While we're at it, refactor the loop slightly. * Fix blocking tests * Make minidom dependency optional (durch#226) * Fix a typo * Make minidom dependency optional * Import futures-io crate directly instead of through futures (durch#227) * Revert "Import futures-io crate directly instead of through futures (durch#227)" This reverts commit 7b2e3a0. * Stream is flaky with rustls-tls * Implements durch#223 * s3/bucket: default to 30-second request timeout (durch#221) No (infinite) timeout is a bad default. * aws-creds 0.27.0 * aws-region 0.23.3 * Import futures-* crates directly instead of through futures (durch#237) * 0.28.0 * No *s Co-authored-by: Paul Khuong <[email protected]> Co-authored-by: Drazen Urch <[email protected]> Co-authored-by: JurajSadel <[email protected]> Co-authored-by: Juraj Sadel <[email protected]> Co-authored-by: Alex Touchet <[email protected]> Co-authored-by: Riley <[email protected]> Co-authored-by: Heikki Linnakangas <[email protected]> Co-authored-by: Jonas Platte <[email protected]>
0.27.0 (durch#218) * bucket: add optional HTTP timeout for all bucket operations (durch#215) And apply the new field in the attohttpc (blocking) and reqwest backends. Surf does not expose such an option, but it's also not as useful in async code: the caller can await with timeout. * Add a request timeout to credentials HTTP GETs (durch#214) Attohttpc sets connection and read timeouts by default. However, by default, there is no timeout on writing the request, nor any end-to-end timeout. Let applications impose one if they want to. * Implement CopyObject bucket operation (durch#211) * Fix sync impl * chore(deps): update dependencies. (durch#209) * chore(deps): update dependencies. * chore: bump aws-creds version to 0.26.1 * Bump all deps * fix edge case of sorting query params for canonical query string in v4 signature (durch#205) * Happy clippy * Better ECS handling * Implement presign_delete (durch#195) * use h1-client-rustls for surf * aws-creds 0.26.2 * 0.27.0 * Update README Co-authored-by: Paul Khuong <[email protected]> Co-authored-by: Johan Thomsen <[email protected]> Co-authored-by: Oscar Rainford <[email protected]> Co-authored-by: Cory Snyder <[email protected]> Co-authored-by: Florian Marending <[email protected]>
PreviousNext