Current Behavior
When the same serverless file is deployed to multiple stages in the same AWS account, use of this plugin fails because the IAM role is the same for the same pipe deployed in multiple stages (e.g. test / staging / production)
Expected Behavior
The IAM role would have a unique name for each stage so that it was possible to deploy multiple stages
Steps to Reproduce the Problem
- use this plugin to define a pipe
- deploy with
npx serverless deploy --stage test
- deploy with
npx serverless deploy --stage staging
- Stack fails to deploy as IAM role for the pipe already exists
Environment