Support connection_draining_timeout_sec in google_compute_region_backend_service

[rileykarson]

Added connection_draining_timeout_sec support to google_compute_region_backend_service.

Regional equivalent to hashicorp/terraform#14559
Part 2/2 for #85
@danawillow

[danawillow]

The regular backend service tests do a final check here that connection draining went back to 0, want to add that to this one too?

[rileykarson]

Done.

[danawillow]

TF_ACC=1 go test ./google -v -run=TestAccComputeRegionBackendService -timeout 120m
=== RUN   TestAccComputeRegionBackendService_basic
--- PASS: TestAccComputeRegionBackendService_basic (74.30s)
=== RUN   TestAccComputeRegionBackendService_withBackend
--- PASS: TestAccComputeRegionBackendService_withBackend (120.03s)
=== RUN   TestAccComputeRegionBackendService_withBackendAndUpdate
--- PASS: TestAccComputeRegionBackendService_withBackendAndUpdate (149.94s)
=== RUN   TestAccComputeRegionBackendService_withConnectionDraining
--- PASS: TestAccComputeRegionBackendService_withConnectionDraining (48.62s)
=== RUN   TestAccComputeRegionBackendService_withConnectionDrainingAndUpdate
--- PASS: TestAccComputeRegionBackendService_withConnectionDrainingAndUpdate (64.03s)
=== RUN   TestAccComputeRegionBackendService_withSessionAffinity
--- PASS: TestAccComputeRegionBackendService_withSessionAffinity (49.34s)
PASS

[dgolja]

I assume this will be released in the 1.0.0 version ?

[rileykarson]

I'm not sure what version number is going to be used for the provider plugin, but this should be present in the first release!

[ghost]

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. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!