-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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: Add support for AL2023 nodeadm
user data
#2942
feat: Add support for AL2023 nodeadm
user data
#2942
Conversation
this is now GA so flipping the switch to |
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.
Looks pretty good. Small question only.
## [20.5.0](v20.4.0...v20.5.0) (2024-03-01) ### Features * Add support for AL2023 `nodeadm` user data ([#2942](#2942)) ([7c99bb1](7c99bb1))
This PR is included in version 20.5.0 🎉 |
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Description
nodeadm
user dataMotivation and Context
Breaking Changes
How Has This Been Tested?
examples/*
to demonstrate and validate my change(s)examples/*
projectspre-commit run -a
on my pull requestToDo
pre
andpost
bootstrap fields from AL2023 templates - this isn't valid/warranted with MIME multi-part