-
Notifications
You must be signed in to change notification settings - Fork 139
feat: implement remote signing transport for S3 requests and add tests #458
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
Open
flarco
wants to merge
10
commits into
apache:main
Choose a base branch
from
flarco:feat/s3-signer-uri
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 4 commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
67dfc1b
feat: implement remote signing transport for S3 requests and add tests
flarco f3d04cc
refactor: remove unsupported S3 properties check and add configurable…
flarco 25bd6e7
fix: improve error logging for remote signature retrieval
flarco f81fe75
fix tests
flarco a9b6d8c
rest purge tables
flarco a2f71aa
feat: enhance S3 remote signing transport to prevent chunked encoding…
flarco af0e730
feat: implement remote signing transport for S3 requests with chunked…
flarco afc4138
fix: update remote signing transport to use string slices for headers…
flarco 7daf9a6
Merge pull request #1 from flarco/feat/rest-purge-tables
flarco 8f38851
undo DropTableOld
flarco File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Personally, I would put this under a separate helper function. wdyt?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, it could be put in the
utilsfolder? Although I don't think this logic will be used elsewhere, so not sure that there is much benefit breaking the function into pieces.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suggest we put it in
io/utils.go. Wdyt @zeroshade ?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
utils folder are generally bad practice, i would even keep this function in this file, or as @dttung2905 proposed in io/utils.go file.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I vote to keep it in this file since there isn't any reusability. But I'm fine moving it as well. Who makes the final call ? 😄
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@flarco it's up to you, same file - it's good enough.