specify --profile for cli #874
Conversation
|
Thanks for the contribution, we should take a look at your pull-request soon and get back |
|
Hi @Brianwithay21, @MalikAtalla-AWS, anything further required before this is eligible for merging? I don't appear to have permission to merge this. |
|
Hey @rrhodes, thanks for the reminder. I'll ping the team who owns this repo. |
No trouble, thanks @MalikAtalla-AWS 🙂 |
| `--profile <value>` | ||
|
|
||
| The AWS profile to use\. If no profile is specified, the client applies credentials specified in the [Boto3 credentials chain](https://boto3.amazonaws.com/v1/documentation/api/latest/guide/configuration.html)\. | ||
|
|
There was a problem hiding this comment.
Would be useful to show how profile should be specified
There was a problem hiding this comment.
Would you mind elaborating on this, please? We have the --profile <value> example above on line 34, consistent with other documented options.
|
I'll look to resolve these merge conflicts, thanks. |
rrhodes
requested review from
ericzbeard and
ammokhov
and removed request for
ericzbeard and
ammokhov
closes #777
Description of changes:
New optional argument
--profileto indicate which AWS profile should be used by the CLI for commandssubmit,invoke, andtest.Testing:
In addition to unit test modifications, the following commands have been manually tested with and without
--profilespecified:submitmodulesubmithooksubmitresourceBy submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.