-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Network_endpoint_group update problem #10363
Comments
Work-around : add the prefix "https://www.googleapis.com/compute/v1/" inside the google_network_endpoint_group.default subnetwork field . |
@ghpu looking at below line in the plan, did you try to provide
|
@edwardmedia , I tried to reference the same content in network and subnetwork. |
@ghpu I don't understand what you mean below. The following config does not make sense to me. Network endpoint groups (NEGs) are zonal resources that represent collections of IP address and port combinations for GCP resources within a single subnet. The
network = google_compute_network.vpc_network.id
subnetwork = google_compute_network.vpc_network.id |
@edwardmedia : My bad, I am not interested in declaring subnetwork. However, if I don"t fill the subnetwork field, the deployment autocompletes it with the same value "https://www.googleapis.com/compute/v1/projects/ino-ols-semafor-api-dev/regions/europe-west1/subnetworks/terraform-network" as found in the expansion of the network field, and so terraform "update" fails because it wants to force "null" value. |
@edwardmedia You are right, I propose to close this bug in favor of #10408 . |
Closing this as below PR is opened |
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. |
Community Note
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 tohashibot
, a community member has claimed the issue already.Description
Network_endpoint_group seems to have its subnetwork content changing adter deployment, which make terraform apply fails when run for update.
Terraform Version
Terraform v1.0.9
on linux_amd64
ghpu@dataguile:~/api$
Affected Resource(s)
google_compute_network_endpoint_group
Terraform Configuration Files
Debug Output
see https://gist.github.com/ghpu/0a8c8998b06c6add2924825e2f42e9e2
Expected Behavior
Apply succeeds , google_compute_network_endpoint_group.default replaced or not changed.
Actual Behavior
Apply fails because google_compute_network_endpoint_group.default already exists. The second call to "terraform apply" has a "forces replacement" for subnetwork
Steps to Reproduce
terraform apply
terraform apply
-> fails the second time at updateImportant Factoids
References
The text was updated successfully, but these errors were encountered: