andreymarchuk / code-pipeline-slack Goto Github PK

Wrap this using AWS Serverless Application Model or Serverless framework.
Potentially post on AWS Serverless Application Repository.

Build Logs button opens invalid CloudWatch Logs urls which does not show logs.

Hi! I tried to run the repo but got no luck. These are the steps I followed:

1. Cloned Repo
2. Set S3 environment variables
3. Uncommented the bottom lines on package.sh
4. Ran package.sh (it seemed to have runned pip install correctly, packaged the cloudformation and uploaded it to S3)
5. Bucket ended with 2 files: template.yml and f03d8c4139a59ac8dc41173a573f7373.
6. Ran the CloudFormation with the S3 URL pointing to my template.yml and supplied the Slack tokens and variables.
7. Stack created successfully, everything seems normal. Push something and trigger CodePipeline, go check Slack and nothing happens.

Lambda runs with error, as described by CloudWatch:

Unable to import module 'notifier': No module named slackclient

Am I missing something here? Is there an issue whilst packaging the lambda with pip's dependencies? Maybe dependencies not making it to S3?

Thanks in advance. Your fork seems to have solved several issues with original one :)

Currently OAuth tokens are stored as Lambda ENV VARS which creates security risk.
Switch to AWS SSM Parameter Store with KMS encryption.

Filter events on CloudWatch event level to reduce lambda invocations.
Currently it receives ton of events which should be discarded.