Stephen Lewis (Burrows)

https://github.com/GoogleCloudPlatform/magic-modules/pull/9965 fixed an issue that could have been caught by this - patch behavior was not properly updated during a promotion.

https://github.com/hashicorp/terraform-provider-google/issues/18091 and https://github.com/hashicorp/terraform-provider-google/issues/18092 would have been caught by this. (7 100% failures)

https://github.com/hashicorp/terraform-provider-google/issues/18239 would have been caught by this.

The following would have been caught by this: - https://github.com/hashicorp/terraform-provider-google/issues/19068 - https://github.com/hashicorp/terraform-provider-google/issues/19070 - https://github.com/hashicorp/terraform-provider-google/issues/19075 - https://github.com/hashicorp/terraform-provider-google/issues/19083

TestAccComputeRegionSecurityPolicyRule_regionSecurityPolicyRuleNetworkMatchUpdate is an example of a test that provisions resources in a region not covered by the related sweeper.

https://github.com/hashicorp/terraform-provider-google/issues/18909 is also impacted by the need for sweeping multiple regions.

b/339860576

@ggtisc this looks like a classic [permadiff](https://googlecloudplatform.github.io/magic-modules/develop/permadiff/), just want to double-check that you weren't able to reproduce it?

@trodge was able to reproduce this permadiff by using an empty `retry_policy` block. For example, ``` resource "google_pubsub_topic" "example" { name = "example-topic" } resource "google_pubsub_subscription" "example" { name =...

@ggtisc `maximum_backoff` and `minimum_backoff` are both `default_from_api` (aka Optional + Computed) which means that if unset in the config, they will continue to send the last value returned from the...