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

Add the ability to specify a profile on the CLI #28

Closed
sesh opened this issue Jul 12, 2016 · 3 comments
Closed

Add the ability to specify a profile on the CLI #28

sesh opened this issue Jul 12, 2016 · 3 comments

Comments

@sesh
Copy link

sesh commented Jul 12, 2016

Some (most?) of us have access to multiple AWS accounts from the command line. It would be super-handy to be able to specify which profile to use with the --profile CLI argument like you can with awscli.

@depado
Copy link

depado commented Jul 12, 2016

A workaround while waiting for this feature :

Store your credentials in your project (and don't version it of course) and change the AWS_CONFIG_FILE environment variable to point to that file before executing chalice. I didn't test it yet but that should do the trick.

@garnaat
Copy link
Collaborator

garnaat commented Jul 12, 2016

You should be able to just set AWS_PROFILE environment variable to pick the desired profile from your standard config file. But I agree having a --profile option makes sense.

@MartijnHarmenzon
Copy link

MartijnHarmenzon commented Jan 14, 2022

I noticed this is possible on deployments also, which is great. But can it also be done on local like:
chalice local --profile my-profile-name

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

No branches or pull requests

5 participants