Closed Robvdhout closed 2 years ago
Oh dear, I found myself going down a miserable rabbit hole seeing why this would be an issue. Ignore me please. I've created a fork for myself and am fully accepting any fallout that would come from it. I'm not going to make you solve the problems AWS seem to have created for themselves
Current Behavior
The default profile only works when using
[default]
and does not work when using[profile default]
as the profile name in.aws\config
Expected Behavior
I would expect it to work when using
[profile default]
Steps to Reproduce the Problem
[profile default]
as the profile name in.aws/config
ssocreds
orssocreds -p default
Environment