Would be great if you could pass in CPU/Memory reservations at the container level when rendering a new task definition.
This would support differing reservations based on environment (as most would resource Prod differently to dev/test for example).
An extra benefit would also be able to support modifying CPU/Memory reservations at the task level too.
Would be great if you could pass in CPU/Memory reservations at the container level when rendering a new task definition.
This would support differing reservations based on environment (as most would resource Prod differently to dev/test for example).
An extra benefit would also be able to support modifying CPU/Memory reservations at the task level too.