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

Made cloudwatch resources optional #43

Merged
merged 3 commits into from
Aug 20, 2023
Merged

Made cloudwatch resources optional #43

merged 3 commits into from
Aug 20, 2023

Conversation

LuizSutil
Copy link
Contributor

When trying to setup ECS service it is creating a "aws_cloudwatch_log_resource_policy" which has a hard limit "Up to 10 CloudWatch Logs resource policies per Region per account. This quota can't be changed."
Created variable to optionally not create cloudwatch log resources.

Relevant issue:
#40

Types of changes

What types of changes does your code introduce to <repo_name>?
Put an x in the boxes that apply

  • Bugfix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation Update (if none of the other choices apply)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

  • I have read the CONTRIBUTING.md doc.
  • I have added necessary documentation (if appropriate).
  • Any dependent changes have been merged and published in downstream modules.

Copy link
Contributor

@mvsnogueira-dnx mvsnogueira-dnx left a comment

Choose a reason for hiding this comment

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

LGTM

@LuizSutil LuizSutil merged commit 6b5a94a into master Aug 20, 2023
5 checks passed
@LuizSutil LuizSutil deleted the ecs_events_optional branch August 20, 2023 23:24
@@ -1,4 +1,5 @@
resource "aws_cloudwatch_log_group" "ecs_events" {
count = var.cloudwatch_logs_create ? 1 : 0
Copy link
Contributor

Choose a reason for hiding this comment

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

Do we need to disable the creation of a new CW log group or the aws_cloudwatch_log_resource_policy only?

@@ -8,6 +9,7 @@ resource "aws_cloudwatch_log_group" "ecs_events" {


resource "aws_cloudwatch_event_rule" "ecs_events" {
count = var.cloudwatch_logs_create ? 1 : 0
name = "capture-ecs-events-${var.cluster_name}-${var.name}"
Copy link
Contributor

Choose a reason for hiding this comment

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

What if I want to use an existing aws_cloudwatch_log_resource_policy?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants