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.

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

Consider moving HTTP Config to base object storage config level #3715

Closed
bwplotka opened this issue Jan 12, 2021 · 3 comments
Closed

Consider moving HTTP Config to base object storage config level #3715

bwplotka opened this issue Jan 12, 2021 · 3 comments

Comments

@bwplotka
Copy link
Member

As per #3657 - it would be nice to have it for all providers as it's a common thing - all providers use HTTP (for now though (: )

Something to consider (:

@GiedriusS
Copy link
Member

Sounds good! However, we should be careful with this to not shoot ourselves in the foot with inconsistencies & compatibility. I'd propose a structure like:

type: s3
config:
  bucket: "foobar"
  ...
transport:
  http2:
    timeout: 10s
  ...

@stale
Copy link

stale bot commented Mar 16, 2021

Hello 👋 Looks like there was no activity on this issue for the last two months.
Do you mind updating us on the status? Is this still reproducible or needed? If yes, just comment on this PR or push a commit. Thanks! 🤗
If there will be no activity in the next two weeks, this issue will be closed (we can always reopen an issue if we need!). Alternatively, use remind command if you wish to be reminded at some point in future.

@stale stale bot added the stale label Mar 16, 2021
@stale
Copy link

stale bot commented Apr 7, 2021

Closing for now as promised, let us know if you need this to be reopened! 🤗

@stale stale bot closed this as completed Apr 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants