fix: Rename var AWS_SESSION_EXPIRATION for aws-vault v7+ #4974
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.
In aws-vault v7.0.0 the authors removed the
AWS_SESSION_EXPIRATION
env var and recommend the use ofAWS_CREDENTIAL_EXPIRATION
. This commit just renames the variable name.Description
A simple rename of the old ENV var that was expected to contain the expiration of the session to the new name.
Motivation and Context
As described in the commit message, aws-vault v7.0.0 no longer sets the variable named
AWS_SESSION_EXPIRATION
with the details of when the session will expire, sostarship
wasn't displaying it anymore.Closes: #4783
I've run the
cargo test
locally on an Apple Silicon and x86 Linux (Ubuntu 22.04 LTS).test result: ok. 951 passed; 0 failed; 32 ignored; 0 measured; 0 filtered out; finished in 0.82s
Screenshots (if appropriate):
How Has This Been Tested?
Checklist: