Sarah French

I've created that new issue here: https://github.com/hashicorp/terraform-provider-google/issues/18109

The PR that closed this issue didn't make VCR tests run using TF 1.8.3 - this PR should do that: https://github.com/GoogleCloudPlatform/magic-modules/pull/10790

Other error messages appear like: ``` vcr_utils.go:144: Step 5/6 error: After applying this test step and performing a `terraform refresh`, the plan was not empty. stdout Terraform used the selected...

This has only failed the past 2 days but given the error message I figured I'd make an issue. The https://status.cloud.google.com/ page doesn't mention any issues

This problem appears to be issues with cleanup of resources after the test ends, due to trying to delete the scopes resource when it's still in use by the binding....

Note from triage: [here's the field in the API](https://cloud.google.com/network-connectivity/docs/reference/networkconnectivity/rest/v1beta/projects.locations.spokes#Spoke.FIELDS.group), and this resource is made via the DCL

Note from triage: It looks like google_certificate_manager_certificate_map is currently [hardcoded to use `global`](https://github.com/hashicorp/terraform-provider-google/blob/2099815f1b9018465102fe621dbd09378c780d9e/google/services/certificatemanager/resource_certificate_manager_certificate_map.go#L184), and [the same is true for google_certificate_manager_certificate_map_entry](https://github.com/hashicorp/terraform-provider-google/blob/2099815f1b9018465102fe621dbd09378c780d9e/google/services/certificatemanager/resource_certificate_manager_certificate_map_entry.go#L205). It may be that when those resources were first added...

Note from triage: this would require adding support for the startingSchema field in the API, [and all its nested fields](https://cloud.google.com/generative-ai-app-builder/docs/reference/rest/v1/projects.locations.collections.dataStores.schemas#resource:-schema).

I'm looking through old issues related to backends and came across this one. From reading through the comments I see that this issue represents the lack of user feedback about...

This looks like an instance of this : https://github.com/hashicorp/terraform-provider-kubernetes/issues/1782 I'll transfer the issue to the hashicorp/terraform-provider-kubernetes repo