Skip to content
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

Override ASG Tag propagation #1091

Closed
2 of 4 tasks
huddy opened this issue Nov 6, 2020 · 3 comments
Closed
2 of 4 tasks

Override ASG Tag propagation #1091

huddy opened this issue Nov 6, 2020 · 3 comments

Comments

@huddy
Copy link
Contributor

huddy commented Nov 6, 2020

I have issues

Firstly thanks very much for maintaining this module, we've received a ton of value from this code.

Currently when passing a list of tags into the module they get applied to both The ASG and instances/workers due to propagate_at_launch defaulting to true.

I have a particular tag that I want applied to all resources including the ASG but except the worker nodes.

A similar PR/Issue has been raised here: #1076 but was rejected with a good suggestion on how to solve this, which I plan to raise a PR for.

I'm submitting a...

  • bug report
  • feature request
  • support request - read the FAQ first!
  • kudos, thank you, warm fuzzy

What is the current behavior?

Currently all tags passed in via var.tags are propagated to ASG and worker nodes.

If this is a bug, how to reproduce? Please include a code sample if relevant.

What's the expected behavior?

Based on the discussion in #1076 it seems there's a desire to solve this by allowing launch templates in the variable worker_groups_launch_template to override var.tags. This would happen for ASGs by using local.asg_tags, so that during processing we use var.workers_group_defaults.tags, thus overriding the var.tag.

Are you able to fix this problem and submit a PR? Link here if you have already.

#1092

Environment details

  • Affected module version: latest/master
  • OS: N/A
  • Terraform version: N/A

Any other relevant info

It would really help although obviously not expected if this would be merged in and tagged fairly soon as this would allow us to ship some functionality we require and I know others are looking forward to this as well!

@barryib
Copy link
Member

barryib commented Nov 7, 2020

Closing this, since #1092 is now merged.

@barryib barryib closed this as completed Nov 7, 2020
@barryib
Copy link
Member

barryib commented Nov 7, 2020

v13.2.0 is now released.

@github-actions
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 23, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants