You mentioned you solved this but I just wanted to reply in case this answer is useful to others who might encounter the same issue:
Unfortunately simultaneously with the Terraform Core beta the Terraform Registry team is also in the process of preparing the registry to support namespaced providers, and part of that is making sure that the providers are all in the right namespace. Previously all providers belonged to a special namespace “terraform-providers”, but now that our provider address model supports namespaces the ones that have contributing teams at HashiCorp have moved into the “hashicorp” namespace.
Most of these moves happened before we released v0.13.0-beta1, but unfortunately the
google-beta provider lagged behind a little due to some technical concerns specific to that provider.
Therefore if you had tried out the
terraform 0.13upgrade command prior to last week it would’ve proposed a source address of
terraform-providers/google-beta for that provider. The correct source address is now
hashicorp/google-beta and those running
terraform 0.13upgrade for the first time today will see the correct result.
If you had previously run a
terraform apply with one of the v0.13.0 beta releases then this older source address would also be encoded in your state. If so, you can also address the problem in the state by running the following command after you see the errors from
terraform state replace-provider 'terraform-providers/google-beta' 'hashicorp/google-beta'
After that, you should be able to run
terraform init again and see it successfully install the Google Cloud Platform Beta provider from the new location.
This situation was an unfortunate collision of two different team’s pre-release processes and is not a situation that should arise again after this change.