Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ability to provide service directory region when generating private service connect (PSC) IP's and forwarding rules for Google APIs #9758

Assignees
Labels
enhancement forward/review In review; remove label to forward service/compute-ipam service/compute-l7-load-balancer size/s tpgtools Issues related to the tpgtools generator

Comments

@kliu47
Copy link

kliu47 commented Aug 10, 2021

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

Currently, when generating a PSC endpoint and forwarding rule using google_compute_global_address & google_compute_global_forwarding_rule, the PSC endpoint in is created in the default service directory region. Request is to be able to provide the region in order to create secondary endpoints for availability.

New or Affected Resource(s)

[beta]
google_compute_global_forwarding_rule
google_compute_global_address

Potential Terraform Configuration

resource "google_compute_global_address" "default" {
  provider     = google-beta
  project      = google_compute_network.network.project
  name         = "global-psconnect-ip"
  address_type = "INTERNAL"
  purpose      = "PRIVATE_SERVICE_CONNECT"
  network      = google_compute_network.network.id
  address      = "10.3.0.5"
}
resource "google_compute_global_forwarding_rule" "default" {
  provider              = google-beta
  project               = google_compute_network.network.project
  name                  = "globalrule"
  target                = "all-apis"
  network               = google_compute_network.network.id
  ip_address            = google_compute_global_address.default.id
  load_balancing_scheme = ""
  region = "us-east4" #new value for region when ip_address is of purpose PRIVATE_SERVICE_CONNECT
}

References

b/196055443

@kliu47 kliu47 changed the title Ability to provide service directory region when generating private service connect (PSC) IP's and forwarding rules Ability to provide service directory region when generating private service connect (PSC) IP's and forwarding rules for Google APIs Aug 10, 2021
@rileykarson rileykarson added this to the Goals milestone Aug 16, 2021
@slevenick slevenick removed this from the Goals milestone Aug 23, 2021
@slevenick slevenick added this to the Near-Term Goals milestone Aug 23, 2021
@upodroid
Copy link
Contributor

missing dcl label

@googlerjk googlerjk self-assigned this Jul 26, 2022
@googlerjk googlerjk pinned this issue Jul 26, 2022
@rileykarson rileykarson unpinned this issue Jul 28, 2022
@c2thorn c2thorn added the tpgtools Issues related to the tpgtools generator label Aug 3, 2022
@c2thorn
Copy link
Collaborator

c2thorn commented Aug 3, 2022

The related field in the REST API is serviceDirectoryRegistrations[].serviceDirectoryRegion

Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 22, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.