I am not sure if removing default value is going to be a breaking change. It seems that GCP behaves like maxUtilization 0.8 when no maxUtilization is specified in UTILIZATION balancing mode.

Hello! I am a robot who works on Magic Modules PRs.

I have detected that you are a community contributor, so your PR will be assigned to someone with a commit-bit on this repo for initial review.

Thanks for your contribution! A human will be with you soon.

@danawillow, please review this PR or find an appropriate assignee.

Hi! I'm the modular magician. Your PR generated some diffs in downstreams - here they are.

Diff report:

Terraform GA: Diff ( 2 files changed, 13 insertions(+), 6 deletions(-))
Terraform Beta: Diff ( 2 files changed, 13 insertions(+), 6 deletions(-))
Ansible: Diff ( 2 files changed, 4 insertions(+), 5 deletions(-))
TF Conversion: Diff ( 1 file changed, 11 insertions(+), 1 deletion(-))
Inspec: Diff ( 1 file changed, 1 insertion(+), 1 deletion(-))

Oops! It looks like you're using an unknown release-note type in your changelog entries:

• REPLACEME

Please only use the types listed in https://github.com/GoogleCloudPlatform/magic-modules/blob/master/.ci/RELEASE_NOTES_GUIDE.md.

I'm not totally sure I understand the purpose of this change. It looks like you don't believe the default for this field should be 0.8, but should instead be 0. Why is that? My impression is that 0.8 is the server-side default, so we set it as the default in the provider so that it shows up in terraform plan output. At the moment, setting the field to 0 will allow you to set the value to 0 if that's what you're looking for.

When I create a backend service with balancing mode RATE from web console, I get a backend service with no max_utilization field instead of one with value 0.8. I have no idea if this affects actual behavior, but maybe we should make it behaves like official client?

This is an optional parameter if the backend's balancingMode is UTILIZATION.
https://cloud.google.com/compute/docs/reference/rest/v1/backendServices

p.s. the provider doesn't set default max_utilization value for region backend service currently.

p.p.s. We ran into some backend utilization web UI bug recently and I doubt that it might affect backend service in RATE mode if max_utilization is set.

Another part of this PR is fixing the hash function. I can separate it into another PR if you think that would be better.