-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug in LoadBalancedEc2Service -- must have at least one of 'memoryLimitMiB' or 'memoryReservationMiB' specified #2263
Closed
Fejuto opened this issue
Apr 14, 2019
· 3 comments
· Fixed by #2463 · May be fixed by MechanicalRock/account-reaper#6
Closed
Bug in LoadBalancedEc2Service -- must have at least one of 'memoryLimitMiB' or 'memoryReservationMiB' specified #2263
Fejuto opened this issue
Apr 14, 2019
· 3 comments
· Fixed by #2463 · May be fixed by MechanicalRock/account-reaper#6
Labels
bug
This issue is a bug.
Comments
Hi @Fejuto, Could you include the example you are trying to run? This validation exists in the task-definition.ts construct, but just want to be clear on your use case. Thanks! |
causes
|
4 tasks
SoManyHs
changed the title
Bug in task-definition.js -- must have at least one of 'memoryLimitMiB' or 'memoryReservationMiB' specified
Bug in LoadBalancedEc2Service -- must have at least one of 'memoryLimitMiB' or 'memoryReservationMiB' specified
May 2, 2019
rix0rrr
pushed a commit
that referenced
this issue
May 6, 2019
Previously, only `memoryLimitMiB` was being set in the constructor. This would cause an unexpected validation error when a LoadBalancedEcsService was instantiated with `memoryReservationMiB` only specified. This fix correctly sets both fields. Fixes #2263
SanderKnape
pushed a commit
to SanderKnape/aws-cdk
that referenced
this issue
May 14, 2019
) Previously, only `memoryLimitMiB` was being set in the constructor. This would cause an unexpected validation error when a LoadBalancedEcsService was instantiated with `memoryReservationMiB` only specified. This fix correctly sets both fields. Fixes aws#2263
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
memoryLimitMiB is not optional at the moment while it should be; validate doesn't check for memoryReservationMiB.
The text was updated successfully, but these errors were encountered: