-
-
Notifications
You must be signed in to change notification settings - Fork 674
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
target group arguments #156
Comments
Hi! That's weird, as far as I could see in the code this values are taken from the target_groups variable, which has no default value, so if you didn't declare them in your manifest they should be null. https://github.com/terraform-aws-modules/terraform-aws-alb/blob/master/main.tf#L67 https://github.com/terraform-aws-modules/terraform-aws-alb/blob/master/main.tf#L68 Could you please share: Thanks!! |
previous your reply I haven't used these arguments in target group module code, also I am not declaring them either in manifest see following code snippet
now I have added L67 & L68 in my target group module definition as shared by you, still it showing addition in terraform plan output
are you considering these are mandatory arguments I am using following versions
|
|
@mkhodave as you can see in the response from @antonbabenko, both arguments are needed for the creation of the aws_lb_target_group resource and so if you do not specify them, they are given a default value of false, that it's what you see this in the plan output |
Thanks @nahuel242 & @antonbabenko for explaining in detail |
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. |
Hi,
I am using this module for creating LB & target group, in target group I am seeing following arguments coming up in
terraform plan
output even I haven't used in module & resource manifest fileslambda_multi_value_headers_enabled
proxy_protocol_v2
from where these arguments referencing ?
The text was updated successfully, but these errors were encountered: