fix: Changed default values for lambda_multi_value_headers_enabled and pro… #160
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Changed the default values for lambda_multi_value_headers_enabled and proxy_protocol_v2 from "null" to "default" in the "aws_lb_target_group" "main" resource
Motivation and Context
As mentioned by @antonbabenko in issue #156 , lambda_multi_value_headers_enabled and proxy_protocol_v2 are booleans so their default value should be also a boolean and not null.
This is also stated in the provider documentation:
https://www.terraform.io/docs/providers/aws/r/lb_target_group.html#proxy_protocol_v2
https://www.terraform.io/docs/providers/aws/r/lb_target_group.html#lambda_multi_value_headers_enabled
It's related to issue #156
Breaking Changes
No
How Has This Been Tested?
I've written a small test without specifying values for lambda_multi_value_headers_enabled and proxy_protocol_v2 and used as module source my forked branch with the fix