StreamAlert is a serverless, realtime data analysis framework which empowers you to ingest, analyze, and alert on data from any environment, using datasources and alerting logic you define.
AWS has added some additional state checking into the lambda deployment lifecycle, however, the current TF provider version doesn't know how to handle this.
Duplicate of https://github.com/airbnb/streamalert/pull/1319 targeting master for a 3.5.1 bug fix.
to: @ryandeivert @Ryxias @chunyong-lin cc: related to: https://github.com/airbnb/streamalert/issues/1318 resolves: https://github.com/airbnb/streamalert/issues/1318 closes: https://github.com/airbnb/streamalert/issues/1318
Background
AWS has added some additional state checking into the lambda deployment lifecycle, however, the current TF provider version doesn't know how to handle this.
https://aws.amazon.com/blogs/compute/coming-soon-expansion-of-aws-lambda-states-to-all-functions/
Users can do a temporary state opt-out via adding
aws:states:opt-outin the description until the 1st of October...The smallest change is to update the TF AWS provider to use a new version of the AWS SDK that can handle this.
Changes
Testing
Steps for how this change was tested and verified