AWS credentials profile from provider is ignored

[apokryfos]

It seems to be using the default credentials profile even when a different one is specified:

provider:  
  profile: my-profile

This results in an error indicating the stack does not exist (because it does not exist under the default profile).

[clementheliou]

Hi Yiannis,

Thanks for reporting this issue.

We currently not support all the solutions provided by Serverless to use AWS credentials or profile as we shared this plugin from our own usage.

As a workaround, is it possible for you to use Serverless CLI option or environment variable (AWS_PROFILE) ?
We currently use the latter option and it properly works.

Also, would you be able to open a pull request to provide us with a possible solution ? This is probably the best way to have a working solution shortly.

Thanks.
Clément