Skip to content
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

Conversation

yannrouillard
Copy link
Contributor

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

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.
@github-actions
Copy link

github-actions bot commented Jun 5, 2023

Community Note

Voting for Prioritization

  • Please vote on this pull request by adding a 👍 reaction to the original post to help the community and maintainers prioritize this pull request.
  • Please see our prioritization guide for information on how we prioritize.
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

For Submitters

  • Review the contribution guide relating to the type of change you are making to ensure all of the necessary steps have been taken.
  • For new resources and data sources, use skaff to generate scaffolding with comments detailing common expectations.
  • Whether or not the branch has been rebased will not impact prioritization, but doing so is always a welcome surprise.

@github-actions github-actions bot added service/globalaccelerator Issues and PRs that pertain to the globalaccelerator service. size/XS Managed by automation to categorize the size of a PR. needs-triage Waiting for first response or review from a maintainer. labels Jun 5, 2023
Copy link

@github-actions github-actions bot left a 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! 😃

@ewbankkit ewbankkit added bug Addresses a defect in current functionality. and removed needs-triage Waiting for first response or review from a maintainer. labels Jun 5, 2023
@github-actions github-actions bot added the tests PRs: expanded test coverage. Issues: expanded coverage, enhancements to test infrastructure. label Jun 5, 2023
Copy link
Contributor

@ewbankkit ewbankkit left a 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

@ewbankkit
Copy link
Contributor

@yannrouillard Thanks for the contribution 🎉 👏.

@ewbankkit ewbankkit merged commit 7c0740c into hashicorp:main Jun 5, 2023
38 checks passed
@github-actions github-actions bot added this to the v5.2.0 milestone Jun 5, 2023
@github-actions
Copy link

github-actions bot commented Jun 9, 2023

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!

@github-actions
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 10, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Addresses a defect in current functionality. service/globalaccelerator Issues and PRs that pertain to the globalaccelerator service. size/XS Managed by automation to categorize the size of a PR. tests PRs: expanded test coverage. Issues: expanded coverage, enhancements to test infrastructure.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug]: Can't apply aws_globalaccelerator_endpoint_group resource after modifying the weight
2 participants