Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NAT Endpoint Independent Mapping has wrong default value (True) #10547

Closed
maxlip opened this issue Nov 11, 2021 · 5 comments
Closed

NAT Endpoint Independent Mapping has wrong default value (True) #10547

maxlip opened this issue Nov 11, 2021 · 5 comments
Labels
breaking-change persistent-bug Hard to diagnose or long lived bugs for which resolutions are more like feature work than bug work service/terraform
Milestone

Comments

@maxlip
Copy link
Contributor

maxlip commented Nov 11, 2021

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
  • Please do not leave +1 or me too comments, they generate extra noise for issue followers and do not help prioritize the request.
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment.
  • If an issue is assigned to the modular-magician user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If an issue is assigned to a user, that user is claiming responsibility for the issue. If an issue is assigned to hashibot, a community member has claimed the issue already.

Terraform Version

TF Version is N/A

Affected Resource(s)

Terraform Configuration Files

# Problem is inappropriate default, so base documented config:
resource "google_compute_router_nat" "nat" {
  name                               = "my-router-nat"
  router                             = google_compute_router.router.name
  region                             = google_compute_router.router.region
  nat_ip_allocate_option             = "AUTO_ONLY"
  source_subnetwork_ip_ranges_to_nat = "ALL_SUBNETWORKS_ALL_IP_RANGES"
  # enable_endpoint_independent_mapping is UNDEFINED

  log_config {
    enable = true
    filter = "ERRORS_ONLY"
  }
}

Debug Output

N/A

Panic Output

N/A

Expected Behavior

enable_endpoint_independent_mapping should be set to FALSE as per NAT/API Docs: https://cloud.google.com/nat/docs/overview#specs-rfcs

"By default, Endpoint-Independent Mapping is disabled when you create a NAT gateway."

Actual Behavior

EIP will be enabled

Steps to Reproduce

Just apply without specifying a value for EIP

Important Factoids

EIP is not for everyone, and unexpected use of EIP has triggered at least one known P1 incident.

References

@maxlip maxlip added the bug label Nov 11, 2021
@edwardmedia edwardmedia self-assigned this Nov 11, 2021
@edwardmedia
Copy link
Contributor

Changing it is a breaking change. Add label accordingly

@edwardmedia edwardmedia removed their assignment Nov 12, 2021
@shijeesh-ns
Copy link

Looks like this got missed while updating the gcloud API.

dark added a commit to dark/magic-modules that referenced this issue Jun 21, 2022
As discussed previously in hashicorp/terraform-provider-google#10547
and GoogleCloudPlatform#5942, the default value for enableEndpointIndependentMapping has
been changed in the API to be `false`.

This commit changes the handling of the flag to point at the upstream
default.
@rileykarson rileykarson added this to the Future Major Release milestone Feb 1, 2023
@rileykarson rileykarson added persistent-bug Hard to diagnose or long lived bugs for which resolutions are more like feature work than bug work and removed bug labels Mar 6, 2023
@shijeesh-ns
Copy link

Let me try to fix this in 5.0.0 branch.

@c2thorn
Copy link
Collaborator

c2thorn commented Sep 11, 2023

closed with GoogleCloudPlatform/magic-modules#8600

This will release with v5.0.0. Check #15582 for more details on the major release.

@github-actions
Copy link

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 12, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
breaking-change persistent-bug Hard to diagnose or long lived bugs for which resolutions are more like feature work than bug work service/terraform
Projects
None yet
5 participants