v1.1.1

What's Changed

• fix log name by @joshgubler in #24
• Bump hashicorp/setup-terraform from 2 to 3 by @dependabot in #23

Full Changelog: v1.1.0...v1.1.1

💥 Breaking 💥

For anything previously deployed, this will be a weird breaking change. terraform apply will probably fail to create the new log group because it already exists (the Lambda would have created it). If this happens to you, the solution is to use terraform import to link the correctly named log group in your terraform project's state file. Alternatively, you could delete the log group and let terraform create it, but this will be a race against any Lambda invocations.

(Yes, I know breaking changes should increment the major version number. But I couldn't bring myself to create v2.0.0 for such a simple bug fix)

v1.1.0

What's Changed

• use oidc for gha aws configuration by @HayLowry in #17
• add optional variables for treat_missing_data and datapoints_to_alarm by @joshgubler in #22
  • Requires TF >= 1.3
• Bump actions/checkout from 3 to 4 by @dependabot in #20

New Contributors

• @HayLowry made their first contribution in #17

Full Changelog: v1.0.3...v1.1.0

v1.0.3

What's Changed

• Alert fix by @dwclogic in #14
• updated README.md to 1.0.3, and dealt with 2 'md' errors Webstorm wa… by @dwclogic in #15
• Alert fix by @dwclogic in #16

Full Changelog: v1.0.2...v1.0.3

v1.0.2

Fix severity code and element_monitor

What's Changed

• Fix Deprecated Github Commands by @jvisker in #13

New Contributors

• @jvisker made their first contribution in #13

Full Changelog: v1.0.1...v1.0.2

v1.0.1

Bump dependency

v1.0.0

First iteration of the Alarms Lambda