-
-
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
Add support for "preserve" argument for addons #2054
Comments
marking as duplicate of #1908 - when that is added this functionality will be supported as well |
actually keeping it open since its not same source 😅 |
This issue has been resolved in version 19.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 this functionality available in the AWS provider for Terraform? See CHANGELOG.md, too.
Describe the solution you'd like.
Add support for
preserve
argument inresource "aws_eks_addon"
, similar to other arguments.Describe alternatives you've considered.
Managing addons out of the module.
Additional context
I understand that AWS v4 has significant breaking changes and not all people can or want to upgrade (though v4.9.0 has improvements in this regard), so for now just probing whether setting min version of aws provider to 4.10.0 in this module is something that would be considered.
The text was updated successfully, but these errors were encountered: