-
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
fix(aws-ecs): add ASG capacity via Capacity Provider by not specifying machineImageType #16361
Conversation
Hi @madeline-k can you help? |
924c117
to
ebfd5f2
Compare
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.
Hi @neilkuan , thanks for working on this! The PR looks really good! I just had one question and a suggestion.
Hi @upparekh , all updated. Please review again, thank you. |
Cluster.addAsgCapacityProvider()
not need specify machineImageType
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.
LGTM! Thanks for your contribution 🚀
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). |
fix(aws-ecs): make
Cluster.addAsgCapacityProvider()
not need specifymachineImageType
close #16360
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license