Skip to content
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

Request: Ability to specify AWS profile the command is run with #6

Closed
jagiles-gg opened this issue Jan 6, 2022 · 8 comments
Closed

Comments

@jagiles-gg
Copy link

Based on observation, it appears that the tool runs using either the default profile, or whatever profile is set in the AWS_PROFILE environment variable.

It would be great if the dialog provided the ability to (optionally) specify a name of the AWS profile to execute the command with. As someone who has access to many AWS accounts and has quite a few in my credentials file, being able to specify which set of credentials the command is executed with would be greatly appreciated.

@coderazzi
Copy link
Owner

coderazzi commented Jan 6, 2022 via email

@jagiles-gg
Copy link
Author

Thank you, sir! Much appreciated.

@coderazzi
Copy link
Owner

coderazzi commented Jan 12, 2022 via email

@jagiles-gg
Copy link
Author

It does work, but the plugin does assume the existence of a ~/.aws/config file. If that file does not exist, then an error dialog pops up and the profile drop down is empty.

You might also fall back to the ~/.aws/credentials file and read profiles from there? I know when using aws configure it puts things in the right place, but the documentation on the CLI does not require that certain properties lie in ~/.aws/config and does allow for all properties to lie in ~/.aws/credentials.

I recognize that this is a non-standard setup so feel free to ignore this particular bit of feedback.

@coderazzi
Copy link
Owner

coderazzi commented Jan 13, 2022 via email

@jagiles-gg
Copy link
Author

Yeah...you can probably feel free to ignore. My configuration was setup manually and not through the CLI. So for me, response format, region, etc is all setup in the credentials file.

I am willing to admit to being in a non-standard setup. If I move those settings to the config file where they are supposed to live I don't see the error.

@coderazzi
Copy link
Owner

coderazzi commented Jan 14, 2022 via email

@coderazzi
Copy link
Owner

coderazzi commented Jan 22, 2022 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants