compute_router_nat subnetwork always changes for LIST_OF_SUBNETWORKS about terraform-google-cloud-nat HOT 7 CLOSED

Well, I decided to rewrite my implementation without any module and the problem immediately become apparent. The resource google_compute_router_nat has block subnetwork that requires argument source_ip_ranges_to_nat with the following description:

(Required) List of options for which source IPs in the subnetwork should have NAT enabled. Supported values include: ALL_IP_RANGES, LIST_OF_SECONDARY_IP_RANGES, PRIMARY_IP_RANGE.

So my error was that I was trying to specify subnetwork's CIDR range (i.e. 10.10.0.0/24) in this argument while it only accepts specific values (i.e. ALL_IP_RANGES, LIST_OF_SECONDARY_IP_RANGES and PRIMARY_IP_RANGE). Cloud-nat module README does not provide information about the possible values of the arguments into its subnetworks block and apparently there is no validation of the passed values, but anyway the problem is resolved now, so let this stay closed for good.

from terraform-google-cloud-nat.

@gdsotirov Glad you got it working and apologies for the confusion.

from terraform-google-cloud-nat.

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days

from terraform-google-cloud-nat.

This is really not to be closed. I'm seeing these "changes" on a daily basis when applying and they are simply annoying. Can someone look into it?

from terraform-google-cloud-nat.

I recommend switching to the cloud-router module: https://github.com/terraform-google-modules/terraform-google-cloud-router

from terraform-google-cloud-nat.

OK @morgante, I'll try it next (working) week and I'll write back whether it solves the problem.

from terraform-google-cloud-nat.

Switching to cloud-router module is not the solution for the problem I reported @morgante, so this issue should not be closed IMHO.

from terraform-google-cloud-nat.