Flaky compute API enablement leading to tainted project when auto_create_network set to false

[bharathkkb]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
• Please do not leave +1 or me too comments, they generate extra noise for issue followers and do not help prioritize the request.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.
• If an issue is assigned to a user, that user is claiming responsibility for the issue.
• Customers working with a Google Technical Account Manager or Customer Engineer can ask them to reach out internally to expedite investigation and resolution of this issue.

Terraform Version & Provider Version(s)

Terraform v1.5.7
on

• provider registry.terraform.io/hashicorp/google v4.84.0

Affected Resource(s)

google_project

Terraform Configuration

google_project with auto_create_network set to false which is default for project factory module

module "project" {
  source  = "terraform-google-modules/project-factory/google"
  version = "~> 14.5"
  name       = "foo"
  project_id = "foo"
  org_id     = var.org_id
  folder_id  = var.folder_id
  billing_account = var.billing_account
}

Debug Output

N/A this was running in CB and flaky

Expected Behavior

No response

Actual Behavior

Got an error during project creation like

Error: Error deleting default network in project foo: Error listing firewall rules in proj: googleapi: Error 403: Compute Engine API has not been used in project foo before or it is disabled. Enable it by visiting...

Steps to reproduce

1. terraform apply

Important Factoids

This seems to be flaky and I was unable to repro locally

References

No response

[bharathkkb]

Looks like this might be fixed in a newer release
GoogleCloudPlatform/magic-modules#10046