fix: Allow optional initProcessEnabled when enable_execute_command is true

[magreenbaum]

Description

Reverts to previous logic here: https://github.com/terraform-aws-modules/terraform-aws-ecs/pull/136/files
This allows user to override optional initProcessEnabled as needed.

Motivation and Context

Closes: #311

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

[bryantbiggs]

thank you!

[antonbabenko]

This PR is included in version 6.0.6 🎉

[nZac]

Thank you @antonbabenko and @magreenbaum!

[robertalexa]

Hey guys, could you double check that this PR actually behaves as expected? I have updated the module at my end and initProcessEnabled changed from true to false in the task definition, despite the enable_execute_command being true. This may be a misunderstanding of how merge works, cause I believe initProcessEnabled has a value of false in .terraform/modules/ecs_service/wrappers/container-definition/main.tf line 34. Either that or I am missing something at my end....

My code:

My post-update task:

My post-update task definition:

My pre-update task definition:

Any chance you can shed some light?

[magreenbaum]

@robertalexa thanks for mentioning this, I've opened this PR to address that: #330

[bryantbiggs]

relates to hashicorp/terraform-provider-aws#17988

[github-actions]

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.