serverless-step-functions
serverless-step-functions copied to clipboard
AWS Step Functions plugin for Serverless Framework ⚡️
# This is a Feature Proposal ## Description The permissions generated, for example with a Lambda triggered by a CloudWatch Notification on a State Machine status change, are generated with...
# This is a (Feature Proposal) ## Description When using a custom `name` in the definition of a step function in serverless, this is obviously intended to populate the `StateMachineName`...
# This is a Bug Report ## Description For bug reports: * What went wrong? Sending HTTP requests to API endpoint `http://:/restapis//local/_user_request_/` returns status code 500: ``` File "/opt/code/localstack/localstack/services/apigateway/apigateway_listener.py", line...
Could I ask why the syntax `!Ref resourceName` does not work here, instead I have to use `#{resourceName}` syntax to reference a Cloudformation resource defined in the template? ```yml stepFunctions:...
Hi, I have an AWS step function that has a number of tasks where I define parameters. Here is an example of one in the AWS States JSON format: ```...
I follow this example about config **CloudWatchLogs** for the **Express Workflow** ```yml stepFunctions: stateMachines: hellostepfunc1: type: EXPRESS loggingConfig: level: ERROR includeExecutionData: true destinations: - Fn::GetAtt: [MyLogGroup, Arn] ``` But It...
# This is a Bug Report ## Description Most of the serverless frame work follows conventions where we can use `{"Fn::GetAtt": ["myFunction", "Arn"]}` which is derived from: ``` functions: myFunction...
# This is a Bug Report ## Description For bug reports: * What went wrong? On latest version of plugin we are now getting an error on package: ``` Invalid...
# This is a Bug Report ## Re-deployment fails with "State Machine Already Exists" error. I have deployed and redeployed several state machines many times. This is the first time...