-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Double Name tags on asg workers #945
Comments
michaelPotter
added a commit
to michaelPotter/terraform-aws-eks
that referenced
this issue
Jul 10, 2020
2 tasks
michaelPotter
added a commit
to michaelPotter/terraform-aws-eks
that referenced
this issue
Jul 10, 2020
I'm seen the same problem |
Fixed in #946 |
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. |
# for free
to subscribe to this conversation on GitHub.
Already have an account?
#.
I have issues
I'm submitting a...
What is the current behavior?
Terraform tries to add two Name tags to autoscaling group workers on every apply.
It looks like the module applies a custom Name tag to autoscaling group workers in addition to the tags passed into the module. Terraform tries to apply two Name tags to the worker resources, and fails silently. During the next plan phase, TF will try to apply double Name tags again.
This clutters up the plan output since it tries to add on every apply.
If this is a bug, how to reproduce? Please include a code sample if relevant.
Pass a custom Name tag to the module
What's the expected behavior?
I think the module should apply only the internal version of the tag (or replace the internal Name tag with something else.)
Are you able to fix this problem and submit a PR? Link here if you have already.
Pull Request: #946
Environment details
Any other relevant info
Here's an example of the output I see on EVERY apply
The text was updated successfully, but these errors were encountered: