You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, with version 0.5.1, users cannot use --profile like they can with aws cli commands. I would like to see --profile supported as it is used in aws cli and Cloud Custodian (https://github.com/capitalone/cloud-custodian).
When users try to use --profile now, they are presented the "usage" text.
The text was updated successfully, but these errors were encountered:
Correct, --profile isn't a supported option. awslimitchecker does not use aws cli, it uses boto3 to interface with the AWS API.
If you wish to use a profile from your ~/.aws/credentials file, you can do so with the AWS_PROFILE environment variable, per the boto credentials documentation.
I just realized that there was an incomplete and untested implementation of this in PR #188. I guess I should try to pick that up and push it across the finish line to close both of these...
Right now, with version 0.5.1, users cannot use --profile like they can with aws cli commands. I would like to see --profile supported as it is used in aws cli and Cloud Custodian (https://github.com/capitalone/cloud-custodian).
When users try to use --profile now, they are presented the "usage" text.
The text was updated successfully, but these errors were encountered: