-
-
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
Drop support for aws_launch_configuration
#1679
Comments
@daroga0002 / @antonbabenko - happy to hear your thoughts |
I agree, and it's a good idea to include it in v18.0.0 if possible. |
I started on a PR last night and will keep working on it - removing launch configuration, converting from |
Yup, I think it is without sense to hold launch configurations as launch templates are for long time and we have node groups |
This issue has been resolved in version 18.0.0 🎉 |
I'm going to lock this issue 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 similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Is your request related to a new offering from AWS?
Is your request related to a problem? Please describe.
Describe the solution you'd like.
aws_launch_configuration
and simplify the module by relying on justaws_launch_template
Describe alternatives you've considered.
Additional context
Because AWS is not adding any new features, and LT has long superseded LC, I think this will greatly help in simplifying a lot of complexity and duplication within the module
The text was updated successfully, but these errors were encountered: