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

Is there equivalent of --profile? #46

Closed
pwinston opened this issue Aug 28, 2019 · 4 comments
Closed

Is there equivalent of --profile? #46

pwinston opened this issue Aug 28, 2019 · 4 comments

Comments

@pwinston
Copy link

pwinston commented Aug 28, 2019

I expected I could use --profile staging and --profile production like aws-cli to access the profiles in my credentials file. Looks like --profile is not supported? Is there another way to access these named profiles?

[staging]
aws_access_key_id = XXXXX
aws_secret_access_key = XXXXX

[production]
aws_access_key_id = XXXX
aws_secret_access_key = XXXX
@kislyuk
Copy link
Owner

kislyuk commented Aug 28, 2019

The standard way to define which AWS CLI profile to use is through the AWS_PROFILE environment variable, which Aegea supports by not interfering with the profile ingestion functionality of the underlying boto3/botocore libraries.

I will consider adding --profile and --region as aegea CLI options.

@pwinston
Copy link
Author

Thank you that works. I use --profile on aws-cli and added that same flag to all our tools. This env var is more than a 80% solution, but --profile is a tiny bit nicer I think.

@kislyuk
Copy link
Owner

kislyuk commented Sep 30, 2019

--profile and --region are now supported in v2.7.3.

@pwinston
Copy link
Author

pwinston commented Oct 2, 2019

Cool thanks for doing that, nice job.

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