Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

backend/s3: Add HTTP parameters for parity with AWS Provider #30496

Closed
Tracked by #33687
gdavison opened this issue Feb 8, 2022 · 1 comment · Fixed by #33765
Closed
Tracked by #33687

backend/s3: Add HTTP parameters for parity with AWS Provider #30496

gdavison opened this issue Feb 8, 2022 · 1 comment · Fixed by #33765
Assignees
@jar-b
Labels
backend/s3 enhancement new new issue not yet triaged

Comments

@gdavison
Copy link
Contributor

gdavison commented Feb 8, 2022 •
edited
Loading

The AWS Provider supports the following parameters. Add them for parity.

  1. http_proxy. Also supports HTTP_PROXY and HTTPS_PROXY environment variables
  2. insecure to allow insecure TLS requests. Defaults to false
  3. use_dualstack_endpoint
  4. use_fips_endpoint
@gdavison gdavison added enhancement backend/s3 new new issue not yet triaged labels Feb 8, 2022
@gdavison gdavison mentioned this issue Aug 15, 2023
Closed
20 tasks
@gdavison gdavison changed the title backend/s3: Add parameters for parity with AWS Provider backend/s3: Add HTTP parameters for parity with AWS Provider Aug 15, 2023
@jar-b jar-b self-assigned this Aug 24, 2023
This was referenced Aug 25, 2023
Closed
Merged
@RLRabinowitz RLRabinowitz mentioned this issue Oct 9, 2023
Closed
@github-actions GitHub Actions
Copy link
Contributor

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 11, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@jar-b jar-b

Labels
backend/s3 enhancement new new issue not yet triaged
Projects
None yet
Milestone
No milestone
2 participants
@gdavison @jar-b