Add Private Service Connect as purpose to resource google_compute_subnetwork

[jeheyer]

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 the issue is assigned to the "modular-magician" user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If the issue is assigned to a user, that user is claiming responsibility for the issue. If the issue is assigned to "hashibot", a community member has claimed the issue already.

Description

When creating a subnet via Terraform, purpose is currently limited to "PRIVATE" or "INTERNAL_HTTPS_LOAD_BALANCER"

New or Affected Resource(s)

• google_compute_subnetwork

Potential Terraform Configuration

resource "google_compute_subnetwork" "psc-subnet" {
  name              = "psc-service1-us-central1"
  ip_cidr_range  = "192.0.2.0/28"
  region             = "us-central1"
  purpose          = "PRIVATE_SERVICE_CONNECT"
  network          = "my-vpc-network"
}

References

I see two requests for connecting to an already published service but nothing related to publishing a service. A dedicated subnet is the first requirement for publishing a service.

• 9758

• 10344

[jeheyer]

Not clear if this is supported in the API yet, even beta:

Method: subnetworks.insert

It has been supported via gcloud and web console for a while.

[upodroid]

Hi

This feature is already supported.

We don't validate the value of purpose.

https://github.com/hashicorp/terraform-provider-google/blob/master/google/resource_compute_subnetwork.go#L196

Thank you

[jeheyer]

Oh I see. Could the documentation be updated so this is clear?

google_compute_subnetwork

[github-actions[bot]]

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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.