-
Notifications
You must be signed in to change notification settings - Fork 9.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
[Bug]: aws_launch_template
can't have "aws-node-termination-handler/managed"
as a key
#30166
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
Relates #24449. |
This functionality has been released in v5.0.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
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. |
Terraform Core Version
1.4.2
AWS Provider Version
4.59.0
Affected Resource(s)
Expected Behavior
When I add the tag
"aws-node-termination-handler/managed"
to an aws_launch_template, it gets added to the AWS resource.Actual Behavior
The tag doesn't get added to the AWS resource.
Relevant Error/Panic Output Snippet
Terraform Configuration Files
Steps to Reproduce
terraform apply
the above config.Debug Output
The provider is stripping the tag and not POSTing at all:
Panic Output
N/A
Important Factoids
Nothing important, this is minimally reproducible.
References
kops attempts to add this tag to the launch templates when you enable the node-termination-handler, which is what revealed this bug. However it's easy enough to manually reproduce with a single line of Terraform.
Would you like to implement a fix?
No
The text was updated successfully, but these errors were encountered: