Why doesn't ComputeRouterNAT expose TCP TIME_WAIT Timeout

[sryabkov]

Describe your question

Out of five NAT timeouts, Config Connector ComputeRouterNAT seems to be exposing only four. Even though it is possible to change TCP TIME_WAIT Timeout using the API or a gcloud command , it is not possible to change it using Config Connector. Why is that?

The parameter is referred to as tcpTimeWaitTimeoutSec in the API and --tcp-time-wait-timeout in gcloud compute routers nats update.

[mbzomowski]

Hi @sryabkov, in order to support this new field, we rely on Terraform adding it to google_compute_router_nat. Please file an enhancement request in terraform-provider-google repository if there isn't one already.

Unfortunately, the timeline for the completion of this request is unpredictable. We highly recommend you contribute to it yourself to accelerate the process, as Terraform is an open source project.

If you have other concerns, or would like to escalate this request, please reach out to us via GCP support.

[sryabkov]

@mbzomowski It seems to have already been added, please see hashicorp/terraform-provider-google#12174

[mbzomowski]

Ah you're right, in that case it'll get picked up the next time we upgrade our terraform provider, likely next week. Then it should be included in the next Config Connector release after that.

[mbzomowski]

@sryabkov correction - we won't be updating our Terraform provider this week. We should be updating it two weeks from now, so this change will be included in our release 3 weeks from now.