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
The google TF provider has a compute_router_nat_address resource that handles the NAT IPs lifecycle automatically for a given compute_router_nat instance. It could be nice to provide this as an option alongside the already existing nat_ips & drain_nat_ips parameters in the nats object.
Design remains open to discussion but the idea would be to give the user a flag to either enable or disable the `compute_router_nat_address` usage when the `nat_ip_allocate_option` is set or defaults to `MANUAL_ONLY`. If the flag is `true`, we would then use the `initial_nat_ips` parameters in the `google_compute_router_nat` resource instead of `nat_ips` & `drain_nat_ips` and add an additional `google_compute_router_nat_address` bloc. A great example is available in the resource documentation page.
Additional information
No response
The text was updated successfully, but these errors were encountered:
TL;DR
The google TF provider has a
compute_router_nat_address
resource that handles the NAT IPs lifecycle automatically for a givencompute_router_nat
instance. It could be nice to provide this as an option alongside the already existingnat_ips
&drain_nat_ips
parameters in thenats
object.Terraform Resources
https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/compute_router_nat_address
Detailed design
Additional information
No response
The text was updated successfully, but these errors were encountered: