Skip to content

Add support for legacy aws_security_token key in credentials file#3

Merged
venth merged 1 commit intoventh:masterfrom
brandond:add_boto_compat
Jul 10, 2016
Merged

Add support for legacy aws_security_token key in credentials file#3
venth merged 1 commit intoventh:masterfrom
brandond:add_boto_compat

Conversation

@brandond
Copy link
Contributor

Ansible uses a weird hybrid of boto and boto3 that doesn't appear to properly support the new AWS_SESSION_TOKEN variable, and instead still looks for AWS_SECURITY_TOKEN. This patch is a monkeypatch for this issue that updates aws-adfs to write the token into the credentials file under both keys.

Ansible uses a weird hybrid of boto and boto3 that [doesn't appear to properly support the new AWS_SESSION_TOKEN variable](boto/boto#3298), and instead still looks for AWS_SECURITY_TOKEN. This patch is a monkeypatch for this issue that updates aws-adfs to write the token into the credentials file under both keys.
@brandond
Copy link
Contributor Author

This one's pretty minor, but I need it for Ansible support - since a majority of the Ansible AWS modules haven't been upgraded to boto3, and the aforementioned issue with boto has not been fixed.

@venth
Copy link
Owner

venth commented Jul 10, 2016

Small indeed 😀 If it would work for ansible, it'll be awesome. Till now I use nasty decorator hack that adds additional header containing session token for every boto call. I'll merge it now. New package I could upload once I'll be back home from a walk with my son 😄 Thanks again.

@venth venth merged commit 50e621b into venth:master Jul 10, 2016
@venth
Copy link
Owner

venth commented Jul 10, 2016

Released ;) Thank you.

@brandond brandond deleted the add_boto_compat branch July 12, 2016 20:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants