`initProcessEnabled` should be optional for `enable_execute_command`

[nZac]

Description

initProcessEnabled is now forcibly enabled whenever passing enable_execute_command = true. While this is a best practice it is optional according to the ECS docs..

It would be great if we could revert this line.

linuxParameters = var.enable_execute_command ? merge(var.linuxParameters, { "initProcessEnabled" : true }) : var.linuxParameters

Back to it's previous approach.

linux_parameters = var.enable_execute_command ? merge({ "initProcessEnabled" : true }, var.linux_parameters) : merge({ "initProcessEnabled" : false }, var.linux_parameters)

So that it is possible to turn it off when the container already has an init process.

If your request is for a new feature, please use the Feature request template.

• ✋ I have searched the open/closed issues and my issue is not listed.

Versions

• Module version [Required]: v6.0.3

• Terraform version: 1.12.1

• Provider version(s): 6+

Reproduction Code [Required]

The standard example will demonstrate this.

Steps to reproduce the behavior:

I'm not using a workspace.
No local cache issues, this is a logic problem.
We upgraded was how we found it.

Expected behavior

I can override the initProcessEnabled setting for a container definition when enable_execute_command is set.

Actual behavior

I can not override the initProcessEnabled setting for a container definition when enable_execute_command is set.

[bryantbiggs]

relates to hashicorp/terraform-provider-aws#17988

[github-actions]

I'm going to lock this issue 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 similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.