Skip to content

Conversation

@desertaxle
Copy link
Member

Closes #19320

- Updated ECSWorker to explicitly include cluster and launchType in the task_run_request if specified in the configuration.
- Added tests to verify that these parameters are correctly passed to the run_task API call, including scenarios where they are missing from the template.
@github-actions github-actions bot added the bug Something isn't working label Nov 3, 2025
@desertaxle desertaxle changed the title 2025 11 03 8f7w c044f Fix missing required parameters in run_task API Call Nov 3, 2025
Fix ECS worker missing cluster and launchType parameters in run_task API call

This PR fixes issue where ECS worker fails to pass cluster and launchType
parameters to AWS ECS run_task API calls, even when correctly configured
in the work pool.

<details>
<summary>Changes</summary>

- Modified  to explicitly ensure cluster and
  launchType are included in the task run request
- Added logic to add cluster from configuration.cluster if missing or empty
- Added logic to default launchType to FARGATE if missing or empty (matching
  the default launch_type variable)
- Ensures these parameters are included even when template variables resolve
  to empty/None
- Preserves existing behavior where launchType is removed when capacity
  provider strategy is set

</details>

Related: #19320
@desertaxle desertaxle marked this pull request as ready for review November 4, 2025 13:58
@desertaxle desertaxle merged commit 75c3726 into main Nov 4, 2025
17 checks passed
@desertaxle desertaxle deleted the 2025-11-03-8f7w-c044f branch November 4, 2025 14:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

ECS Worker Missing Required Parameters in run_task API Call

3 participants