Please Support google_compute_region_ssl_certificate as a Data Source

[sfc-gh-jihuang]

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

google_compute_ssl_certificate, the GLOBAL SSL certificate, is available as a data source in Terraform, but google_compute_region_ssl_certificate, the REGIONAL SSL certificate, is NOT. For users who do not wish to create SSL certificates using Terraform and upload the regional certificate via an out-of-band process, this gap is unacceptable.

New or Affected Resource(s)

• google_compute_region_ssl_certificate

Potential Terraform Configuration

data "google_compute_region_ssl_certificate" "wildcard_gcptest1_deployment" {
  name    = local.ssl_certificate_name
  project = var.project_id
}

References

Please consult the documentation for the global SSL certificate: https://www.terraform.io/docs/providers/google/d/compute_ssl_certificate.html

[ghost]

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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!