
First I created a notification rule for my pipeline.

Rule creation would require a name ( obviously ) and events that should be notified and a target system that the notification should send.
Since I would prefer to receive all the events, I choose all and Slack as the target.

Since my newly created Slack channel is not yet registered as a target I attempted target creation.

Not it is time for me to configure the chatbot. I create a new client.

AWS offered me two options for the client Slack and AWS Chime, I proceed with Slack and it directed me to Slack for authorization for the Slack workspace.


Once I authorized, there are a few more additional configurations needed to do.
What Slack channel should be connected to? What sort of privileges I should allow to the chatbot and what are the guard rules I should create?

Since my only intention is to view what's going on with my CI/CD pipeline, I just set AWS read-only access for both allowed rule and guard conditions.
I triggered my pipeline and started to flood my channel with all the events.


Làm việc trong ngành phát triển phần mềm được một thời gian, tôi nhận ra một điều thú vị: không phải lúc nào code đẹp cũng đồng nghĩa với thành công về mặt kinh doanh. Hãy cùng tôi đi sâu vào một vài ví dụ điển hình và bài học từ thực tế.
Beiryu
Contributor

Event-driven architecture, Reactive programming, and technologies like NodeJS, Play, and
Beiryu
Contributor