-
-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use profile different than default #29
Comments
unfortunately, there is not yet any functionality to switch profiles on the fly. however, as a workaround, you can potentially just install multiple versions of this workflow that are each configured to utilize a different profile and prefix. have a look at this comment for more details. i have not tested this myself, and it is somewhat of a hack, but it seems like there has been some success doing it this way |
Thank you I will give it a try :) |
Ok It is working but partially for example : if I go to the loggroups of a lambda in dev with the aws command it oppens me my browser with my last active session (preprod). |
@rkoval I recommend to create a command like: aws setprofile. Then it parse the ~/.aws/credential file and give the availalbe profile list. Then you can persist the value in a file like |
Hi, I would like to use this workflow to administrate our infrastructure.
But it does not match our need because we do not have only one profile but at least 3 like :
Can we imagine a way to switch between profile before to use a command like :
aws go prod
-> switch the profile to prodOr a way to specify it in the request :
aws prod ec2 instances plop
I am openned to participate to this feature.
The text was updated successfully, but these errors were encountered: