Inconsistent gcp naming convention for terraform resources

Oct 29, 2025

About

Uh? I've recently had to deploy a load balancer system in GCP, and the terraform resource types for the components that make it up use inconsistent naming conventions.

I'm drawing a table to illustrate.

Illustration

	Region qualifier in name	Missing qualifier in name	Global qualifier in name
Region resource	google_compute_region_url_map google_compute_region_target_https_proxy google_compute_region_backend_service google_compute_region_network_endpoint_group	google_compute_forwarding_rule google_compute_address
Zonal resource		google_compute_network_endpoint_group
Regional or global resource depending on location attribute		google_certificate_manager_certificate google_certificate_manager_dns_authorization
Global resource		google_compute_managed_ssl_certificate google_compute_url_map google_compute_target_https_proxy google_compute_backend_service google_compute_network_endpoint_group	google_compute_global_forwarding_rule google_global_compute_address google_compute_global_network_endpoint_group