-
Notifications
You must be signed in to change notification settings - Fork 4.3k
revert(ecs): add validation checks to memory cpu combinations of FARGATE compatible task definitions #34155
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
Conversation
…f FARGAT…" This reverts commit 734ca66.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #34155 +/- ##
=======================================
Coverage 84.00% 84.00%
=======================================
Files 121 121
Lines 6984 6984
Branches 1179 1179
=======================================
Hits 5867 5867
Misses 1005 1005
Partials 112 112
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
} | ||
} else { | ||
throw new Error(`If operatingSystemFamily is ${runtimePlatform.operatingSystemFamily!._operatingSystemFamily}, then cpu must be in 1024 (1 vCPU), 2048 (2 vCPU), or 4096 (4 vCPU). Provided value was: ${cpu}`); | ||
if (Number(cpu) === 1024) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Going back to no token check is worrying me a bit. But given that this PR is a pure revert, I am biasing toward approving.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this should be safe because Number(any non-number value)
will be a NaN
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One comment but approving
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
Comments on closed issues and PRs are hard for our team to see. |
Reverts #33608
Closes #34157
This is a breaking change because
cpu
property allows input like1vcpu
although it's not documented in the public CFN documentation.This would mean that the reverted PR will cause regression on CDK app that looks like below