You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-added logging module so we get pretty JSON display in CloudWatch Logs
-added support for CodePipeline S3 Source (no revisionUrl)
-log the error field if it is returned by channels.history or channels.list (helped with troubleshooting)
-support new bot user with combined oauth bot user token and oauth token
-updated readme with instructions to install with the new Slack App's bot user
Copy file name to clipboardExpand all lines: readme.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,14 +25,16 @@ When creating the CloudFormation stack, you can customize:
25
25
-`SlackBotName` (defaults to `PipelineBuildBot`).
26
26
-`SlackBotIcon` (defaults to `:robot_face:` 🤖 ).
27
27
28
-
Additionally, you must provide `SlackToken`, (see [BotUsers](https://api.slack.com/custom-integrations/bot-users) for creating a slack bot user with an integration token).
28
+
Additionally, you must provide both a `SlackOAuthAccessToken` and a `SlackBotUserOAuthAccessToken`, (see [BotUsers](https://api.slack.com/bot-users) for creating a slack bot user with an OAuth token). It is required to add the permission scope 'Access user’s public channels' (channels:history).
29
+
29
30
30
31
## How it works
31
32
32
33
We utilize [CloudWatch Events](https://docs.aws.amazon.com/AmazonCloudWatch/latest/events/WhatIsCloudWatchEvents.html) for CodePipline and CodeBuild to get notified of all status changes.
33
34
34
35
Using the notifications, as well as using the CodePipeline APIs, we are able to present a unified summary of your Pipeline and Build status.
35
36
37
+
36
38
### IAM permissions
37
39
38
40
As part of the deployment, we create an IAM policy for the bot lambda function of:
0 commit comments