First off, great little tool, we are very happy to use it.
This issue is to consider dropping support for AWS_SECURITY_TOKEN. AWS switched over its usage 6 years ago and most documentation only references AWS_SESSION_TOKEN now. By retaining it, I believe it can only create confusion. Indeed, in our case if created some hard to track down issues when: the standard environment variables were updated and we forgot to update AWS_SECURITY_TOKEN env var as well.
My proposal would be the following:
- Remove default export of
AWS_SECURITY_TOKEN, but perhaps allow it to be exported if a configuration is set.
I'm happy to open a PR, but would like to get any comments/concerns first.
First off, great little tool, we are very happy to use it.
This issue is to consider dropping support for
AWS_SECURITY_TOKEN. AWS switched over its usage 6 years ago and most documentation only referencesAWS_SESSION_TOKENnow. By retaining it, I believe it can only create confusion. Indeed, in our case if created some hard to track down issues when: the standard environment variables were updated and we forgot to update AWS_SECURITY_TOKEN env var as well.My proposal would be the following:
AWS_SECURITY_TOKEN, but perhaps allow it to be exported if a configuration is set.I'm happy to open a PR, but would like to get any comments/concerns first.