Closed solgarius closed 4 years ago
@solgarius Another way to fix this is to change the plugin to use AwsProvider.request() function instead of instantiating AWS.CloudFormation directly. This way you'd be using the same mechanism as Serverless to interact with the AWS SDK, including handling of credentials,
@coyoteecd Good point. I've reworked the plugin so that it now uses the aws provider using getProvider('aws'). Thanks for the suggestion.
Can we please merge this ASAP @aghadiry ? This is currently broken for me. In master branch, there are no exceptions thrown when awsCredentials.credentials is empty and the AWS requests hang. Basically all the awsCredentials.credentials references should be awsCredentials, this is using the latest serverless version and aws-sdk ^2.700.0.
now supported for different versions of AWS SDK/serverless framework. Fix for #17