From the course: Using Slack and AWS EventBridge to Automate Your DevOps Tasks

Unlock the full course today

Join today to access over 22,600 courses taught by industry experts or purchase this course individually.

Next steps

Next steps

- As this code is constantly going to be evolving, let me give you a few considerations for next steps. You may have noticed that I added the stage of the pipeline to the notification messages. So now it says stage source and a stage build along with the name of the pipeline, as well as the notification status in this case started or succeeded, but it could be failed as well. I'll provide you with an updated copy in the exercise files, going back to our Lambda console here in our main function. As you saw, we only have a response to the run pipeline command seen here in line 10. So for next steps, you could certainly add a lot more functionality here in response to other commands, such as reactions, to pull requests in your code repositories. Other actions around code pipeline, for example, something that would happen when a fail notification takes place, the possibilities are endless. And finally, you may be wondering why…

Contents