Improved to add option for Session Token Period Second #10
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.
Relevant Issue (if applicable)
n/a
Details
This library does not support session token generation(login processing) for STS/SSO, etc., so normally it is necessary to write the session token in Credentials(
.aws/<file>
or environment variables).Therefore, to update the Session Token, you will need to use an external program to update the Credential.
However, it is not possible to specify an expiration date for Session Token, so the expiration date is always determined to be in the future.
Therefore, there is a problem that s3fs continues to use an expired Session Token.
(Even if s3fs determines that the Session Token has expired, there is no process to update it, so you need to notice this phenomenon and update it using another program.)
Added an option to specify the validity period(in seconds) of the Session Token in this PR.(This probably doesn't help much.)
Please see the revised README.md for details.