Skip to content

fix: Set logConfiguration to null if empty to prevent ECS errors #323

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

mo36924
Copy link

@mo36924 mo36924 commented Jul 22, 2025

Description

Set logConfiguration to null if empty to prevent ECS errors.
fix #318
ref #91 #217

Motivation and Context

Breaking Changes

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

@@ -47,7 +47,7 @@ locals {
interactive = var.interactive
links = local.is_not_windows ? var.links : null
linuxParameters = local.is_not_windows ? { for k, v in local.linuxParameters : k => v if v != null } : null
logConfiguration = local.logConfiguration
logConfiguration = length(local.logConfiguration) > 0 ? local.logConfiguration : null
Copy link
Member

Choose a reason for hiding this comment

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

this does not match what is described in the title - we'll need a reproduction or proof of this working as intended

Copy link
Author

@mo36924 mo36924 Jul 23, 2025

Choose a reason for hiding this comment

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

this does not match what is described in the title

Which parts specifically do not match?

The details of the error and how to deal with it are as follows.
If create_cloudwatch_log_group is set to false, local.logConfiguration will be an empty object. As a result, the required field logConfiguration.logDriver is not filled in and an error occurs.
This response avoids the error by checking the number of elements in local.logConfiguration and returning null if it is an empty object.

This error is the same as the error fixed in #91.
The problem solved in #91 has reoccurred due to the response in #217.
I think this PR will solve #318.

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.

Service module forces you to specify a log driver or enable cloudwatch in v6
2 participants