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
We're in the unfortunate position to have [] in our AWS account names like this: Company Name [production].
granted sso generate happily generates a config with these account names, but using them results in an error. Is it possible to automatically strip these characters out?
The profile doesn't appear in the list when I run assume, but when I attempt to use the profile via environment variable I get:
❯ export AWS_PROFILE='Company-Name-[production]/RoleName'
❯ aws sts get-caller-identity
Error when retrieving credentials from custom-process: [!] The profile Company-Name-[production]/RoleName cannot be loaded because the name contains one or more of these characters '\][;'"'
[i] Try renaming the profile to 'Company-Name-[production]/RoleName'
[✘] profile not found
Alternative Solutions Considered
For now I've just been renaming the generated profiles manually. I've also re-generated using the template parameter and account ID instead. Both of these work fine TBH, but it'd be nice to have the generate command automatically remove the invalid characters.
The text was updated successfully, but these errors were encountered:
Problem
We're in the unfortunate position to have
[]
in our AWS account names like this:Company Name [production]
.granted sso generate
happily generates a config with these account names, but using them results in an error. Is it possible to automatically strip these characters out?Example generated config:
The profile doesn't appear in the list when I run
assume
, but when I attempt to use the profile via environment variable I get:Alternative Solutions Considered
For now I've just been renaming the generated profiles manually. I've also re-generated using the template parameter and account ID instead. Both of these work fine TBH, but it'd be nice to have the generate command automatically remove the invalid characters.
The text was updated successfully, but these errors were encountered: