-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
Feature request: cross_zone_load_balancing support for aws_lb #3574
Comments
You'll be happy to know there is an open PR already. 😄 I'll mark it to close this ticket when its merged. |
Support has been merged into master and will release with v1.11.0 of the AWS provider, likely in about a week. 🎉 |
Awesome. Thanks. 🍾 |
This has been released in version 1.11.0 of the AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. |
This is somewhat causing issues for me. I'm using an ALB, which does not support this attribute, but Terraform still says:
See #4168. Shouldn't Terraform ignore this attribute for ALBs? |
@israel-tk can you share your config? |
I'm using AWS plugin terraform-provider-aws_v1.13.0_x4 and terraform 0.10.8. This is the relevant part of the config (slightly edited for privacy reasons):
|
The thing is I also see that there is a CC: @bflad |
The fix for suppressing non-applicable attributes in aws_lb diffs was made in #4032 and released in version 1.14.0 of the AWS provider. |
Awesome, thanks a lot and sorry for the noise! |
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
Can you add the following new directive and support for
cross_zone_load_balancing
in the aws_lb resource? This was recently released https://aws.amazon.com/about-aws/whats-new/2018/02/network-load-balancer-now-supports-cross-zone-load-balancing/.The text was updated successfully, but these errors were encountered: