-
-
Notifications
You must be signed in to change notification settings - Fork 275
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
Add support for authenticating access to S3 buckets using temporary credentials #3086
Closed
Closed
Changes from 14 commits
Commits
Show all changes
17 commits
Select commit
Hold shift + click to select a range
2c53ba6
ros3: enabled debugging, stats, and curl verbosity; fixed some bad fo…
aivazis 7c4d68b
ros3: added {session_token} to {H5FD_ros3_fapl_t}
aivazis 750725e
ros3: added {session_token} support to the {ros3} test driver
aivazis 33b17c5
ros3: added support for the AWS {session_token}
aivazis 06272d7
ros3: added {session_token} support to the {s3comms} test driver
aivazis e4cddcc
ros3: created macros with the maximum buffers sizes for the authoriza…
aivazis bdf48e5
ros3: the stats bin boundaries are computed only once during the firs…
aivazis 362ef6d
test/vfd: added an initializer for the new {session_token} field in t…
aivazis f71a4a1
tools: added an initializer for the new {session_token} field in the …
aivazis c4a47f3
ros3: added structure to the debug levels
aivazis 0e3bb0d
Merge branch 'HDFGroup:develop' into ros3
aivazis cfdeebe
Committing clang-format changes
github-actions[bot] b4a9394
Merge branch 'HDFGroup:develop' into ros3
aivazis 376570b
ros3: the access pattern log now includes the size of the file
aivazis 11453ba
Merge branch 'HDFGroup:develop' into ros3
aivazis c32f8eb
ros3: disabled the DEBUG macros to measure performance
aivazis 3677552
Merge branch 'HDFGroup:develop' into ros3
aivazis 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 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
This file contains 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.
Changing a struct in a public header breaks binary compatibility so this change could not be merged downstream to 1.14, etc.
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.
the change comes with a bump in
H5FD_CURR_ROS3_FAPL_T_VERSION
, so it is easy to detect clients that have not been recompiled against the updated headers/library. we should be able to restore binary compatibility. shall we walk through the use cases, or are you guys happy to say this is a 1.15 fix?