-
-
Notifications
You must be signed in to change notification settings - Fork 318
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
Additional tag map isn't actually merged in with the tags #90
Comments
Hrm... if that's the case, it seems to be a bug. Can you check the |
👍 Doesn't seem that the tests cover this currently. The fix should probably use |
It technically "works as designed", but I agree it's confusing. We can fix that. See this for some context. #18 I am open to discussion on how to fix this. The original feature was added by @Jamie-BitFlight who can maybe add additional context. Now this is over 2 years ago, so my memory could be totally incorrect.
So it appears we added this for a narrow use-case specifically with Elastic Beanstalk. ElasticBeanstalk needs tags passed as a |
Closing as "works as designed" and documented by #99 |
I'v recently updated to TF 0.12 and I noticed that changes to the
additional_tag_map
variable does nothing. I've also noticed that the additional tags no longer exist in any of our resources. I'm not exactly sure, but seems as though the following line inmain.tf
is missing a reference tovar.additional_tag_map
.The line is where the
tags
local is being set, and it is:I believe the correction should be:
Making this change locally seems to have done the trick for me, but I might be missing something.
The text was updated successfully, but these errors were encountered: