Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: LogGroup #24

Closed

Conversation

AnkithaBH
Copy link

Description

Currently, the module enforces cloud watch log group for Redis. Added a variable named "create_cloudwatch_log_group" to provide flexibility of choice to the end user, to leverage or not to leverage via this module.

Motivation and Context

Why is this change required? What problem does it solve?
Enhances flexibility and effective internal usage.

How Has This Been Tested?

Could not use the existing examples as we have our own way of deriving networking information and for other reasons.
Created own/separate example which is not included in the code.
Tested the example code by enabling and disabling "create_cloudwatch_log_group" variable.
Both are working without any issues.
pre-commit run -a is executed successfully before creating PR.

@@ -26,10 +26,10 @@ resource "aws_elasticache_cluster" "this" {
ip_discovery = var.ip_discovery

dynamic "log_delivery_configuration" {
for_each = { for k, v in var.log_delivery_configuration : k => v if var.engine != "memcached" && !local.in_replication_group }
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@bryantbiggs
Copy link
Member

Why is this change required? What problem does it solve?
Enhances flexibility and effective internal usage.

That doesn't explain anything

Copy link

github-actions bot commented Dec 1, 2024

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 Dec 1, 2024
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.

2 participants