You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using the aws-sso-util tool to manage all my SSO profiles.
There's a neat command, called populate which automatically reads all profiles from a specified SSO start URL and stores them in the AWS config.
The AWS config for an autopopulated profile looks like the following:
The bug happens, when I want to add a profile (e.g. amazon-aws-cool-account-dev.AWSAdministratorAccess).
It isn't listed at all.
So I only can add those profiles, if I manually rename all of them (awww!).
Guess it's about the dot (.)
If I manually rename the profile name in my AWS config, it's working out.
The text was updated successfully, but these errors were encountered:
Turns out that some INI parsers parse a dot in the name as a path indicator used for nesting. The INI parser we are using https://www.npmjs.com/package/ini (30 million downloads) seem to this as well, npm/ini#22. I did a workaround knowing and it seems to be working, even with more dots and deeply nested objects.
Some background details
I'm using the aws-sso-util tool to manage all my SSO profiles.
There's a neat command, called
populate
which automatically reads all profiles from a specified SSO start URL and stores them in the AWS config.The AWS config for an autopopulated profile looks like the following:
Bug description
The bug happens, when I want to add a profile (e.g. amazon-aws-cool-account-dev.AWSAdministratorAccess).
It isn't listed at all.
So I only can add those profiles, if I manually rename all of them (awww!).
Guess it's about the dot (.)
If I manually rename the profile name in my AWS config, it's working out.
The text was updated successfully, but these errors were encountered: