Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature: support Status Change notification #197

Closed
theburningmonk opened this issue May 9, 2019 · 5 comments · Fixed by #198
Closed

Feature: support Status Change notification #197

theburningmonk opened this issue May 9, 2019 · 5 comments · Fixed by #198
Labels

Comments

@theburningmonk
Copy link
Collaborator

This is a Feature Proposal

Description

You can monitor the execution of your state machines via CloudWatch Events now.

It will be great to add support for it in the plugin so you can configure them alongside your state machine definition, e.g.

stepFunctions:
  stateMachines:
    hellostepfunc1:
      name: test
      definition:
        ...
      notifications:
        ABORTED:
          - sns: SNS_TOPIC_ARN
          - sqs: SQS_TOPIC_ARN
          - sqs: # more config options
              arn: SQS_TOPIC_ARN
              messageGroupId: 12345
          - lambda: LAMBDA_FUNCTION_ARN
          - kinesis: KINESIS_STREAM_ARN
          - kinesis:  # more config options
               arn: KINESIS_STREAM_ARN
               partitionKeyPath: $.user_id
          - firehose: FIREHOSE_STREAM_ARN
          - stepFunctions: STATE_MACHINE_ARN
        FAILED:
          ... # same as above
        RUNNING:
          ... # same as above
        SUCCEEDED:
          ... # same as above
        TIMED_OUT:
          ... # same as above
@horike37
Copy link
Collaborator

horike37 commented May 9, 2019

@theburningmonk
Thank you for the proposal 👍
Sure, let's support for it.

@horike37
Copy link
Collaborator

horike37 commented May 9, 2019

Have this already support for CloudFormation? Since the all deployment is running via it for consistency.

@theburningmonk
Copy link
Collaborator Author

theburningmonk commented May 9, 2019 via email

@horike37
Copy link
Collaborator

horike37 commented May 9, 2019

OK. No problem 👍

@theburningmonk
Copy link
Collaborator Author

🎉 This issue has been resolved in version 1.20.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

ss-betseqnzr pushed a commit to BetSEQNZR/serverless-step-functions that referenced this issue Sep 8, 2023
ss-betseqnzr pushed a commit to BetSEQNZR/serverless-step-functions that referenced this issue Sep 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants