You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+5-2Lines changed: 5 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,10 @@
1
1
## 0.3.1 (February 11, 2026)
2
2
BUG FIXES:
3
-
* add variable grant_pubsub_editor support for autoscaling deployment templates Service Account IAM Role module
4
-
* add new roles/compute.viewer IAM requirement to the CC Service Account for better autoscaler detection and identification
3
+
* add variable grant_pubsub_editor support for autoscaling deployment templates Service Account IAM Role module with default enabled
4
+
* add new custom role creation with ["compute.autoscalers.list", "compute.autoscalers.get"] IAM requirement to the CC Service Account for better autoscaler detection and identification. *This may require additioinal Terraform Service account permissions like Role Administrator
5
+
6
+
ENHANCEMENTS:
7
+
* rename variable image_name to custom_image name to better differentiate between variable marketplace_image
| <aname="input_ccvm_instance_type"></a> [ccvm\_instance\_type](#input\_ccvm\_instance\_type)| Cloud Connector Instance Type |`string`|`"n2-standard-2"`| no |
95
95
| <aname="input_credentials"></a> [credentials](#input\_credentials)| Path to the service account json file for terraform to authenticate to Google Cloud |`string`| n/a | yes |
96
+
| <aname="input_custom_image_name"></a> [custom\_image\_name](#input\_custom\_image\_name)| Custom image name to be used for deploying Cloud Connector appliances. Ideally all VMs should be on the same Image as templates always pull the latest from Google Marketplace. This variable is provided if a customer desires to override/retain an old ami for existing deployments rather than upgrading and forcing a replacement. It is also inputted as a list to facilitate if a customer desired to manually upgrade select CCs deployed based on the cc\_count index |`string`|`""`| no |
96
97
| <aname="input_default_nsg"></a> [default\_nsg](#input\_default\_nsg)| Default CIDR list to permit workload traffic destined for Cloud Connector |`list(string)`| <pre>[<br/> "0.0.0.0/0"<br/>]</pre> | no |
97
98
| <aname="input_fw_cc_mgmt_hcp_vault_address_name"></a> [fw\_cc\_mgmt\_hcp\_vault\_address\_name](#input\_fw\_cc\_mgmt\_hcp\_vault\_address\_name)| The name of the compute firewall created on the user defined Cloud Connector Management VPC Network permitting CC to access to HCP Vault Address port number |`string`|`null`| no |
98
99
| <aname="input_fw_cc_mgmt_ssh_ingress_name"></a> [fw\_cc\_mgmt\_ssh\_ingress\_name](#input\_fw\_cc\_mgmt\_ssh\_ingress\_name)| The name of the compute firewall created on the user defined Cloud Connector Management VPC Network permitting SSH inbound from the VPC CIDR range by default |`string`|`null`| no |
99
100
| <aname="input_fw_cc_mgmt_zssupport_tunnel_name"></a> [fw\_cc\_mgmt\_zssupport\_tunnel\_name](#input\_fw\_cc\_mgmt\_zssupport\_tunnel\_name)| The name of the compute firewall created on the user defined Cloud Connector Management VPC Network permitting CC to establish zssupport tunnel |`string`|`null`| no |
100
101
| <aname="input_fw_cc_service_default_name"></a> [fw\_cc\_service\_default\_name](#input\_fw\_cc\_service\_default\_name)| The name of the compute firewall created on the user defined Cloud Connector Service VPC Network permitting workload traffic to be sent to Zscaler |`string`|`null`| no |
101
-
| <aname="input_grant_pubsub_editor"></a> [grant\_pubsub\_editor](#input\_grant\_pubsub\_editor)| If true, grant roles/pubsub.editor to the CCVM SA at project scope |`bool`|`false`| no |
102
+
| <aname="input_grant_pubsub_editor"></a> [grant\_pubsub\_editor](#input\_grant\_pubsub\_editor)| If true, grant roles/pubsub.editor to the CCVM SA at project scope |`bool`|`true`| no |
| <aname="input_hcp_vault_address"></a> [hcp\_vault\_address](#input\_hcp\_vault\_address)| Customer managed HashiCorp Vault URL; including leading https (if applicable) and trailing port number |`string`|`""`| no |
104
105
| <aname="input_hcp_vault_enabled"></a> [hcp\_vault\_enabled](#input\_hcp\_vault\_enabled)| True/False used to determine specific HCP Vault configured network firewall and Service Account IAM roles. Default is false |`bool`|`false`| no |
@@ -107,7 +108,6 @@ From base_1cc directory execute:
107
108
| <aname="input_hcp_vault_role_name"></a> [hcp\_vault\_role\_name](#input\_hcp\_vault\_role\_name)| Customer managed HashiCorp Role Name |`string`|`""`| no |
108
109
| <aname="input_hcp_vault_secret_path"></a> [hcp\_vault\_secret\_path](#input\_hcp\_vault\_secret\_path)| Customer managed HashiCorp Vault secret path. The path to a secret is formed from three parts: <namespace>/<enginemountpoint>/<pathtosecret>. If you are not using the enterprise version of Vault, you should omit the first part |`string`|`""`| no |
109
110
| <aname="input_http_probe_port"></a> [http\_probe\_port](#input\_http\_probe\_port)| Port number for Cloud Connector cloud init to enable listener port for HTTP probe from GCP LB |`number`|`50000`| no |
110
-
| <aname="input_image_name"></a> [image\_name](#input\_image\_name)| Custom image name to be used for deploying Cloud Connector appliances. Ideally all VMs should be on the same Image as templates always pull the latest from Google Marketplace. This variable is provided if a customer desires to override/retain an old ami for existing deployments rather than upgrading and forcing a replacement. It is also inputted as a list to facilitate if a customer desired to manually upgrade select CCs deployed based on the cc\_count index |`string`|`""`| no |
111
111
| <aname="input_instance_group_name"></a> [instance\_group\_name](#input\_instance\_group\_name)| The name of the Instance Group Manager. Must be 1-63 characters long and comply with RFC1035. Supported characters include lowercase letters, numbers, and hyphens |`list(string)`| <pre>[<br/> ""<br/>]</pre> | no |
112
112
| <aname="input_instance_template_name"></a> [instance\_template\_name](#input\_instance\_template\_name)| The name of the instance template. Conflicts with variable instance\_template\_name\_prefix |`string`|`""`| no |
113
113
| <aname="input_instance_template_name_prefix"></a> [instance\_template\_name\_prefix](#input\_instance\_template\_name\_prefix)| Creates a unique Instance Template name beginning with the specified prefix. Conflicts with variable instance\_template\_name |`string`|`""`| no |
Copy file name to clipboardExpand all lines: examples/base_1cc/variables.tf
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -149,7 +149,7 @@ variable "zones" {
149
149
default=[]
150
150
}
151
151
152
-
variable"image_name" {
152
+
variable"custom_image_name" {
153
153
type=string
154
154
description="Custom image name to be used for deploying Cloud Connector appliances. Ideally all VMs should be on the same Image as templates always pull the latest from Google Marketplace. This variable is provided if a customer desires to override/retain an old ami for existing deployments rather than upgrading and forcing a replacement. It is also inputted as a list to facilitate if a customer desired to manually upgrade select CCs deployed based on the cc_count index"
155
155
default=""
@@ -296,6 +296,6 @@ EOT
296
296
297
297
variable"grant_pubsub_editor" {
298
298
type=bool
299
-
default=false
299
+
default=true
300
300
description="If true, grant roles/pubsub.editor to the CCVM SA at project scope"
| <aname="input_ccvm_instance_type"></a> [ccvm\_instance\_type](#input\_ccvm\_instance\_type)| Cloud Connector Instance Type |`string`|`"n2-standard-2"`| no |
96
96
| <aname="input_credentials"></a> [credentials](#input\_credentials)| Path to the service account json file for terraform to authenticate to Google Cloud |`string`| n/a | yes |
97
+
| <aname="input_custom_image_name"></a> [custom\_image\_name](#input\_custom\_image\_name)| Custom image name to be used for deploying Cloud Connector appliances. Ideally all VMs should be on the same Image as templates always pull the latest from Google Marketplace. This variable is provided if a customer desires to override/retain an old ami for existing deployments rather than upgrading and forcing a replacement. It is also inputted as a list to facilitate if a customer desired to manually upgrade select CCs deployed based on the cc\_count index |`string`|`""`| no |
97
98
| <aname="input_default_nsg"></a> [default\_nsg](#input\_default\_nsg)| Default CIDR list to permit workload traffic destined for Cloud Connector |`list(string)`| <pre>[<br/> "0.0.0.0/0"<br/>]</pre> | no |
98
99
| <aname="input_domain_names"></a> [domain\_names](#input\_domain\_names)| Domain names fqdn/wildcard to have Google Cloud DNS zone forward ZPA App Segment DNS requests to Cloud Connector |`map(any)`| n/a | yes |
99
100
| <aname="input_fw_cc_mgmt_hcp_vault_address_name"></a> [fw\_cc\_mgmt\_hcp\_vault\_address\_name](#input\_fw\_cc\_mgmt\_hcp\_vault\_address\_name)| The name of the compute firewall created on the user defined Cloud Connector Management VPC Network permitting CC to access to HCP Vault Address port number |`string`|`null`| no |
100
101
| <aname="input_fw_cc_mgmt_ssh_ingress_name"></a> [fw\_cc\_mgmt\_ssh\_ingress\_name](#input\_fw\_cc\_mgmt\_ssh\_ingress\_name)| The name of the compute firewall created on the user defined Cloud Connector Management VPC Network permitting SSH inbound from the VPC CIDR range by default |`string`|`null`| no |
101
102
| <aname="input_fw_cc_mgmt_zssupport_tunnel_name"></a> [fw\_cc\_mgmt\_zssupport\_tunnel\_name](#input\_fw\_cc\_mgmt\_zssupport\_tunnel\_name)| The name of the compute firewall created on the user defined Cloud Connector Management VPC Network permitting CC to establish zssupport tunnel |`string`|`null`| no |
102
103
| <aname="input_fw_cc_service_default_name"></a> [fw\_cc\_service\_default\_name](#input\_fw\_cc\_service\_default\_name)| The name of the compute firewall created on the user defined Cloud Connector Service VPC Network permitting workload traffic to be sent to Zscaler |`string`|`null`| no |
103
-
| <aname="input_grant_pubsub_editor"></a> [grant\_pubsub\_editor](#input\_grant\_pubsub\_editor)| If true, grant roles/pubsub.editor to the CCVM SA at project scope |`bool`|`false`| no |
104
+
| <aname="input_grant_pubsub_editor"></a> [grant\_pubsub\_editor](#input\_grant\_pubsub\_editor)| If true, grant roles/pubsub.editor to the CCVM SA at project scope |`bool`|`true`| no |
| <aname="input_hcp_vault_address"></a> [hcp\_vault\_address](#input\_hcp\_vault\_address)| Customer managed HashiCorp Vault URL; including leading https (if applicable) and trailing port number |`string`|`""`| no |
106
107
| <aname="input_hcp_vault_enabled"></a> [hcp\_vault\_enabled](#input\_hcp\_vault\_enabled)| True/False used to determine specific HCP Vault configured network firewall and Service Account IAM roles. Default is false |`bool`|`false`| no |
@@ -109,7 +110,6 @@ From base_1cc_zpa directory execute:
109
110
| <aname="input_hcp_vault_role_name"></a> [hcp\_vault\_role\_name](#input\_hcp\_vault\_role\_name)| Customer managed HashiCorp Role Name |`string`|`""`| no |
110
111
| <aname="input_hcp_vault_secret_path"></a> [hcp\_vault\_secret\_path](#input\_hcp\_vault\_secret\_path)| Customer managed HashiCorp Vault secret path. The path to a secret is formed from three parts: <namespace>/<enginemountpoint>/<pathtosecret>. If you are not using the enterprise version of Vault, you should omit the first part |`string`|`""`| no |
111
112
| <aname="input_http_probe_port"></a> [http\_probe\_port](#input\_http\_probe\_port)| Port number for Cloud Connector cloud init to enable listener port for HTTP probe from GCP LB |`number`|`50000`| no |
112
-
| <aname="input_image_name"></a> [image\_name](#input\_image\_name)| Custom image name to be used for deploying Cloud Connector appliances. Ideally all VMs should be on the same Image as templates always pull the latest from Google Marketplace. This variable is provided if a customer desires to override/retain an old ami for existing deployments rather than upgrading and forcing a replacement. It is also inputted as a list to facilitate if a customer desired to manually upgrade select CCs deployed based on the cc\_count index |`string`|`""`| no |
113
113
| <aname="input_instance_group_name"></a> [instance\_group\_name](#input\_instance\_group\_name)| The name of the Instance Group Manager. Must be 1-63 characters long and comply with RFC1035. Supported characters include lowercase letters, numbers, and hyphens |`list(string)`| <pre>[<br/> ""<br/>]</pre> | no |
114
114
| <aname="input_instance_template_name"></a> [instance\_template\_name](#input\_instance\_template\_name)| The name of the instance template. Conflicts with variable instance\_template\_name\_prefix |`string`|`""`| no |
115
115
| <aname="input_instance_template_name_prefix"></a> [instance\_template\_name\_prefix](#input\_instance\_template\_name\_prefix)| Creates a unique Instance Template name beginning with the specified prefix. Conflicts with variable instance\_template\_name |`string`|`""`| no |
Copy file name to clipboardExpand all lines: examples/base_1cc_zpa/variables.tf
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -149,7 +149,7 @@ variable "zones" {
149
149
default=[]
150
150
}
151
151
152
-
variable"image_name" {
152
+
variable"custom_image_name" {
153
153
type=string
154
154
description="Custom image name to be used for deploying Cloud Connector appliances. Ideally all VMs should be on the same Image as templates always pull the latest from Google Marketplace. This variable is provided if a customer desires to override/retain an old ami for existing deployments rather than upgrading and forcing a replacement. It is also inputted as a list to facilitate if a customer desired to manually upgrade select CCs deployed based on the cc_count index"
155
155
default=""
@@ -300,6 +300,6 @@ EOT
300
300
301
301
variable"grant_pubsub_editor" {
302
302
type=bool
303
-
default=false
303
+
default=true
304
304
description="If true, grant roles/pubsub.editor to the CCVM SA at project scope"
0 commit comments