Closed varun1231 closed 3 years ago
I'm seeing the same issue. Using big sur 11.3 with awsume 4.5
Looks like I missed the step about setting up the alias. Once I added the alias, things started working https://awsu.me/general/quickstart.html#alias-setup
Yep, the alias should be setup in order to allow awsume to modify your current shell's environment variables. We recently released 4.5.1, which improves the awsume-configure
command so that if you run it without any flags (so just awsume-configure
), it'll try to set everything up for each shell you have installed based on sane defaults, so this could be used to help setup awsume if the installation process doesn't work right
Closing for now, but if you still experience issues please reopen this issue or open a new one, thanks!
+1, happens as of now. I ran "awsume profile" with everything set up correctly, still no AWS_PROFILE variable.
Running awsume
profile-name
isn't setting environment variableAWS_PROFILE
and therefore, I am unable to use it directly with terraform. I have to export that variable separately. It does however setAWSUME_PROFILE
. Seen below are debug logs as I ran the last awsume with --debug flag.And get the following error when trying to do
awsume -a
Note: Mac OSX version is Big Sur 11.2.3