Skip to content

Conversation

@magreenbaum
Copy link
Member

Description

Add log anomaly detection support.

Motivation and Context

Breaking Changes

No.

How Has This Been Tested?

  • I have updated at least one of the examples/* to demonstrate and validate my change(s)
  • I have tested and validated these changes using one or more of the provided examples/* projects
  • I have executed pre-commit run -a on my pull request

@antonbabenko antonbabenko merged commit e62a3b7 into terraform-aws-modules:master Dec 19, 2024
33 checks passed
antonbabenko pushed a commit that referenced this pull request Dec 19, 2024
## [5.7.0](v5.6.1...v5.7.0) (2024-12-19)

### Features

* Add Log Anomaly Detection Support ([#74](#74)) ([e62a3b7](e62a3b7))
@antonbabenko
Copy link
Member

This PR is included in version 5.7.0 🎉

@magreenbaum magreenbaum deleted the feat/log_anomaly_detector branch December 20, 2024 11:46
@albertsj1
Copy link

I don't understand why the aws provider was bumped to version = ">= 5.81". This breaks our pipelines because this issue is still not fixed, so we have to lock the provider to ~> 5.68.0 in order for terraform to not hang on arm64. :(

@antonbabenko
Copy link
Member

@albertsj1 This PR adds support for aws_cloudwatch_log_anomaly_detector resource type which was introduced in v5.81.0, so we require this version. There is not much we can do in this module.

@github-actions
Copy link

github-actions bot commented Feb 7, 2025

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 7, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants