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

feat: add option to S3 backend for V2 signatures #352

Merged
merged 1 commit into from Nov 23, 2020

Conversation

simonswine
Copy link
Contributor

What this PR does:

Adds a config option/flag to use signature version 2 in the S3 backend. This will switch from the default V4 auth to a V2, which might be necessary for some object storage implementations.

Which issue(s) this PR fixes:
Fixes #<issue number
Checklist

  • Tests updated
  • Documentation added
  • CHANGELOG.md updated - the order of entries should be [CHANGE], [FEATURE], [ENHANCEMENT], [BUGFIX]

@CLAassistant
Copy link

CLAassistant commented Nov 19, 2020

CLA assistant check
All committers have signed the CLA.

tempodb/backend/s3/s3.go Outdated Show resolved Hide resolved
@simonswine simonswine force-pushed the add-v2-signatures-option branch 2 times, most recently from 5bb63c2 to 8a15717 Compare November 23, 2020 15:11
@simonswine simonswine marked this pull request as ready for review November 23, 2020 15:12
Currently we don't expose any ability to select the signature version
used for our S3 backend.

Signed-off-by: Christian Simon <simon@swine.de>
Copy link
Member

@joe-elliott joe-elliott left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@joe-elliott joe-elliott merged commit aa26d61 into grafana:master Nov 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants