-
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
fix: ensure endpoint group weight 0 is taken into account #31767
fix: ensure endpoint group weight 0 is taken into account #31767
Conversation
Zero is a valid value for an endpoint group configuration and it shouldn't be ignored and not sent to the API. The current behaviour causes a endpoint weight of 128 to be used instead as it is AWS default value if no weight is set. This causes traffic to be sent despite the expectations that a zero value will cause no traffic on the endpoint.
Community NoteVoting for Prioritization
For Submitters
|
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.
Welcome @yannrouillard 👋
It looks like this is your first Pull Request submission to the Terraform AWS Provider! If you haven’t already done so please make sure you have checked out our CONTRIBUTOR guide and FAQ to make sure your contribution is adhering to best practice and has all the necessary elements in place for a successful approval.
Also take a look at our FAQ which details how we prioritize Pull Requests for inclusion.
Thanks again, and welcome to the community! 😃
…ting 'endpoint_configuration.weight' to '0'.
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.
LGTM 🚀.
% make testacc TESTARGS='-run=TestAccGlobalAcceleratorEndpointGroup_ALBEndpoint_clientIP' PKG=globalaccelerator ACCTEST_PARALLELISM=2
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./internal/service/globalaccelerator/... -v -count 1 -parallel 2 -run=TestAccGlobalAcceleratorEndpointGroup_ALBEndpoint_clientIP -timeout 180m
=== RUN TestAccGlobalAcceleratorEndpointGroup_ALBEndpoint_clientIP
=== PAUSE TestAccGlobalAcceleratorEndpointGroup_ALBEndpoint_clientIP
=== CONT TestAccGlobalAcceleratorEndpointGroup_ALBEndpoint_clientIP
--- PASS: TestAccGlobalAcceleratorEndpointGroup_ALBEndpoint_clientIP (843.01s)
PASS
ok github.com/hashicorp/terraform-provider-aws/internal/service/globalaccelerator 848.794s
@yannrouillard Thanks for the contribution 🎉 👏. |
This functionality has been released in v5.2.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
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. |
Zero is a valid value for an endpoint group configuration and it shouldn't be ignored and not sent to the API.
The current behaviour causes a endpoint weight of 128 to be used instead as it is AWS default value if no weight is set. This causes traffic to be sent despite the expectations that a zero value will cause no traffic on the endpoint.
Description
This Pull request fix the issue #31254 where a zero value for a global accelerator endpoint group configuration is ignored despite being a valid value.
Relations
Closes #31254
References
https://docs.aws.amazon.com/global-accelerator/latest/api/API_EndpointConfiguration.html