terraform-aws-slackbot

Full Changelog: https://github.com/amancevice/terraform-aws-slackbot/compare/v25.0.5...v25.1.0

Full Changelog: https://github.com/amancevice/terraform-aws-slackbot/compare/v25.0.4...v25.0.5

Bugfix to event OpenAPI integration and state machine

Upgrade Lambda runtime to python3.12

Bugfixes to API Gateway domain name (should be REGIONAL, not EDGE)

Re-architect project to use native API Gateway -> Step Functions integration for better latency

Python ~> 3.11

bump aws provider to ~> 5.0

Update to python3.10 runtime

Pipenv upgrade

v24 of this module represents a re-thinking of this module. Previous versions attempted to be as un-opinionated as possible, while this version is more of a "batteries included" approach.

Prerequisites

In order to use this module you must set up a Route53 hosted zone and an ACM certificate that covers the domain on which your Slack API will be hosted (eg, *.example.com or slack.example.com)

Resources

This module will create the following resources:

• API Gateway HTTP API (+ supporting resources
• EventBridge event bus
• SecretsManager secret container
• Lambda functions
• CloudWatch log groups

Post-requisites

After applying this module you must update the SecretsManager secret with the JSON for your Slackbot (see README)

Upgrade to Python 3.9
Add option to format JSON logs

Support for terraform v1.0
Fix to OAuth route

Upgrade runtime to python3.9
Requires aws provider ~> 3.55

The included function to make requests against the Slack API from EventBridge events was modified to be more generic
If the event contains a task-token key, this value is used to issue success/failure notifications for Step Functions

This release marks a complete overhaul of the application—rewritten from the ground up!

Runtime

The NodeJS runtime of the application was dropped in favor Python. This was done for two reasons: first and foremost, the cold start time of Lambda functions using the Python runtime appears to be shorter than its peers. Since Slack imposes a strict time limit on many of their features, shaving milliseconds is paramount. Second, I am much more comfortable coding in Python than I am NodeJS, so I hope this change means more stability and maintainability going forward.

Events

Events are now published to EventBridge instead of SNS. This was done because the strength EventBridge's pattern matching capabilities means that some of the application logic intended to extract SNS message attributes could be removed.

Additionally, I was able to roll the essential features of the slackbot-chat into this main module so that users are able to publish events to EventBridge and have them be forwarded to Slack's Web API.

slackbot ~> 4.9.0
improvements to logging

Terraform 0.14 compatibility