-
Notifications
You must be signed in to change notification settings - Fork 9.7k
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
provider/google: Fix google_compute_backend_service max_utilization backend attribute #5075
Conversation
Fixes issue hashicorp#4985 by correcting copy/paste error that caused the max_utilization attribute to be read from the max_rate_per_instance attribute. N.B. There is still no test coverage for this issue.
i can rebase and force update if that's better than merge commits. |
Hi @billf! Thanks for this change - it clearly resolves a bug. For future reference, we ask that people don't edit the commit log in branches, and update it on merge. Thanks for the contribution! |
provider/google: Fix google_compute_backend_service max_utilization backend attribute
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. |
N.B. There is still no test coverage for this issue.