search

kislyuk / aegea

Amazon Web Services Operator Interface
Apache License 2.0
68 stars 17 forks source link

Is there equivalent of --profile? #46

Closed pwinston closed 5 years ago

pwinston commented 5 years ago

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 commented 5 years ago

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 commented 5 years ago

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 commented 5 years ago

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

pwinston commented 5 years ago

Cool thanks for doing that, nice job.