-
-
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
fix: Update autoscaling group tags
-> tag
to support v4 of AWS provider
#1866
fix: Update autoscaling group tags
-> tag
to support v4 of AWS provider
#1866
Conversation
@@ -378,6 +406,15 @@ resource "aws_autoscaling_group" "this" { | |||
} | |||
} | |||
|
|||
dynamic "tag" { | |||
for_each = { for tag in local.asg_tags : "${tag.key}-${tag.value}" => tag } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same comment as in another PR - terraform-aws-modules/terraform-aws-autoscaling#179
It is so much cleaner now! 🚀 |
### [18.6.1](v18.6.0...v18.6.1) (2022-02-15) ### Bug Fixes * Update autoscaling group `tags` -> `tag` to support v4 of AWS provider ([#1866](#1866)) ([74ad4b0](74ad4b0))
This PR is included in version 18.6.1 🎉 |
### [18.6.1](terraform-aws-modules/terraform-aws-eks@v18.6.0...v18.6.1) (2022-02-15) ### Bug Fixes * Update autoscaling group `tags` -> `tag` to support v4 of AWS provider ([#1866](terraform-aws-modules/terraform-aws-eks#1866)) ([1892b1e](terraform-aws-modules/terraform-aws-eks@1892b1e))
I'm going to lock this pull request 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 related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Description
tags
->tag
to support v4 of AWS provider. This is now a dynamictag
block and the current functionality has been preserved through a map comprehension statement. The variablevar.propagate_tags
has been removed as part of this change and users should pass any tags through the normalvar.tags
variable nowMotivation and Context
tags
on autoscaling groupBreaking Changes
var.propagate_tags
is removed andvar.tags
is used in its place so I am (controversially) electing to not mark this as a breaking change (does not affect a significant population of users and there is a clear path to mitigate without state changes or downtime)How Has This Been Tested?
examples/*
projects