-
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
feat(batch): fargate support for jobs #15848
Conversation
const isFargate = ComputeResourceType.FARGATE === props.computeResources.type | ||
|| ComputeResourceType.FARGATE_SPOT === props.computeResources.type; | ||
|
||
if (!isFargate) { |
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.
Better to avoid code that bypasses the type-system if we can. You can just compute the values before initializing the computeEnvironment
and use them
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.
Done
}; | ||
|
||
if (!isFargate) { | ||
Object.assign(containerProperties, { |
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.
Same - just compute before needing to use it, and declare the types it uses so its easy to navigate and deep dive.
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.
Done
/** | ||
* Whether or not to assign a public IP to the job | ||
*/ | ||
export enum AssignPublicIp { |
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.
This seems funky, can we not just convert all of this to a boolean?
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.
Yes
@DDynamic Thanks for reviving this! |
@iliapolo should be ready for a final pass. |
@DDynamic found a couple of more stuff that caught my eye, but I feel good we can merge this soon enough. Thanks! |
@iliapolo ready for another pass. Thanks for the through review! |
Any chance this is going to be merged in soon? hanging out for this feature and it looks complete. |
…plify network config
@madeline-k 👋 I see you're now the assignee for aws-batch PRs and issues. Would you mind helping to bring this to completition? |
Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
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 master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
Added Fargate support for Batch jobs.
Note: this is not entirely my work - most of it was done by @kokachev. It is an updated version of Fargate support for batch jobs based on the feedback left in #13591.
ResourceRequirements
for Fargate jobscloses: #13590, #13591
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license