Repository navigation
Test downstream HTTP and crypto configurations - #869
Draft
RanaPriyansh wants to merge 1 commit into
Draft
RanaPriyansh wants to merge 1 commit into
RanaPriyansh wants to merge 1 commit into
Conversation
alamb
marked this pull request as draft
October 16, 2026 21:21
Contributor
|
Marking as draft per #873 (comment) so i can find the PRs that need attention. Thank you |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Which issue does this PR close?
Closes #759.
Rationale for this change
The current feature matrix checks library flags. It does not show whether downstream applications can select HTTP and crypto dependencies and run a request.
What changes are included in this PR?
Add six independent downstream examples. Each example sends a signed S3 PUT with fake credentials. Replace the targeted proxy Clippy and dependency-tree checks with formatting, Clippy, runtime, and normal-dependency checks for each example.
Are there any user-facing changes?
The examples document downstream dependency choices. There is no public API change.
All six examples passed local formatting, Clippy with warnings denied, a signed PUT, and dependency checks. Root
cargo test --offlinepassed: 99 tests and 31 doctests passed. The S3 endpoint is local or in memory. HTTPS certificate validation and live cloud services were not tested.Codex used.