Release 3.10.23 - Retain the cpu and memory properties at the task level#309
Merged
Conversation
forevermatt
approved these changes
Mar 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixed
cpuandmemoryproperties if specified at the task level. This required a change to use jq to identify which properties are included in the original task definition because a simple regular expression would not differentiate between container-level and task-level properties with the same name. Addresses RegisterTaskDefinition fails for task def with only task-level memory when re-registering to update image #308.Feature PR Checklist
test.batsfile)Release PR Checklist
ecs-deployscriptRelease _._._ - Summary of change(using whateverthe new version number is, plus a succinct summary of what changed)