Closed asherber closed 1 year ago
Thanks for reporting. I will upgrade to latest AWS CLI and follow up.
To reproduce, delete your config
file and start fresh with aws configure sso
. Enter an SSO session name when prompted -- otherwise it will create a "legacy" config
file that doesn't make use of sessions.
(Apology, was away with early '22 holidays. Be back on 1.1.0 release milestone for start of 2023. ETA end Jan / early Feb)
Hi there; sorry for delay. New year start with a bit of backlogs.
This is now avail for public review with rc1
.
https://pypi.org/project/yawsso/1.1.0rc1/
pip install -U yawsso==1.1.0rc1
Nothing much. Just use yawsso
as usual. It now recognise the new style sso-session config section. Still backward compatible at the same time.
I will test it myself a bit; these days. If all good, it will come GA when 1.1.0 milestone close.
The RC is working for me, thanks!
Thanks for testing and feedback
Sorry, didn't have time to look at this the last couple of days, but so far working fine today.
Cool, thanks again for feedback. Work well over my end too, so far.
I will probably push it through other pending tickets; and we can make GA release over this weekend then.
This is now released and GA. https://github.com/victorskl/yawsso/releases/tag/1.1.0
pip install -U yawsso==1.1.0
I'm setting up a brand new machine, and it appears that AWS (I'm using CLI v2.9.1 on Windows) has introduced a new kind of SSO configuration since the last time I did this.
In short, by pulling some of the common SSO settings out into their own section in the config, AWS gains the ability to automatically refresh the SSO session credentials that may be used by different profiles.
This is causing problems with yawsso, which is looking for specific keys in the profile section.
Old-style
config
fileNew-style config file