-
Notifications
You must be signed in to change notification settings - Fork 4k
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(ecs): enable Kernel 5.10 support on Amazon Linux 2 #29809
base: main
Are you sure you want to change the base?
Conversation
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.
The pull request linter has failed. See the aws-cdk-automation comment below for failure reasons. If you believe this pull request should receive an exemption, please comment and provide a justification.
A comment requesting an exemption should contain the text Exemption Request
. Additionally, if clarification is needed add Clarification Request
to a comment.
✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.
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.
The pull request linter has failed. See the aws-cdk-automation comment below for failure reasons. If you believe this pull request should receive an exemption, please comment and provide a justification.
A comment requesting an exemption should contain the text Exemption Request
. Additionally, if clarification is needed add Clarification Request
to a comment.
✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.
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.
The pull request linter has failed. See the aws-cdk-automation comment below for failure reasons. If you believe this pull request should receive an exemption, please comment and provide a justification.
A comment requesting an exemption should contain the text Exemption Request
. Additionally, if clarification is needed add Clarification Request
to a comment.
✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.
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.
Thanks 👍
I left some suggestions for adjustments.
Also, does the recommended
here refer to the kernel version? 🤔
If so, we should remove it when kernel
is specified.
I am not sure what Both of the following commands return a valid AMI from SSM
and
|
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.
Thanks 👍
Left some comments for further adjustments, feel free to comment on those.
/** | ||
* Kernel version used. | ||
* Only supported for Amazon Linux 2. | ||
* | ||
* @default none, uses the recommended kernel version | ||
*/ | ||
readonly kernel?: ec2.AmazonLinux2Kernel; |
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.
Discussed offline, this should not be undeprecated...sorry about that, I was wrong. This entire props should be deprecated and replaced with the linked EcsOptimizedImage
instead.
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.
@comcalvi I replied to your comment here. Can you have a look?
This entire props should be deprecated and replaced with the linked EcsOptimizedImage instead.
EcsOptimizedImage
is a class and its private constructor is still using the deprecated EcsOptimizedAmiProps
. There are no other Props interfaces for EcsOptimizedImage
constructor.
Is it time to remove @deprecated
already?
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.
It looks like we deprecated the props and decided to create a bunch of factory methods that take an Options
instead of props
. I think your original solution was actually correct; leave these as deprecated (since they should be marked internal, and if we remove the deprecation we'll never remember to fix this) and just add the new property.
@TheRealAmazonKendra is correct about this, in principle, since a deprecated marker implies that these props have been directly replaced by something else. That is not what is going on here. Instead, these props are supposed to be hidden away behind a set of factory methods. So, even if we had not missed these when we did v2, the optimal would still be what you've done here; add kernel
to these props.
Sorry for the churn on this one, please leave the @deprecated
and add the new property to those deprecated props.
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.
@comcalvi Thanks for the update 🙏
I am not entirely confident I am following what has been the final decision regarding how this change should be incorporated but I tried to revert to a previous state in this branch history; namely (c107fe0).
Please let me know if I misunderstood your last comment. Thanks again
This PR has been in the BUILD FAILING state for 3 weeks, and looks abandoned. To keep this PR from being closed, please continue work on it. If not, it will automatically be closed in a week. |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Issue
#29800
Reason for this change
Allow using recommended kernel version instead of 4.14 which is marked as EOL Jan 2024, by opting in for the new kernel.
Description of changes
amazonLinux2
in favor of a newamazonLinux2WithKernel510
.Description of how you validated changes
Unit and integration tests.
Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license