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

google_compute_router_peer force recreation #4481

Closed
alterdinosu opened this issue Sep 18, 2019 · 2 comments
Closed

google_compute_router_peer force recreation #4481

alterdinosu opened this issue Sep 18, 2019 · 2 comments
Labels
bug forward/review In review; remove label to forward service/compute-router

Comments

@alterdinosu
Copy link

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

Terraform v0.11.13

Affected Resource(s)

google_compute_router_peer add advanced routing options , hashicorp/terraform-provider-google-beta#1104 force new resource without advertise_mode or with advertise_mode set to DEFAULT or CUSTOM.

An example

google_compute_router_peer.gcp-xyz-rtr01-1 (new resource required)
id: "asia-east1/mgmt-router-taiwan/gcp-xyz-rtr01-1" => (forces new resource)
advertise_mode: "" => "DEFAULT" (forces new resource)
advertised_route_priority: "100" => "100"
interface: "xyz-rtr01-1" => "xyz-rtr01-1"
ip_address: "169.254.163.10" =>
name: "gcp-xyz-rtr01-1" => "gcp-xyz-rtr01-1"
peer_asn: "64526" => "64526"
peer_ip_address: "169.254.163.11" => "169.254.163.11"
project: "mgmt-23919" =>
region: "asia-east1" => "asia-east1"
router: "mgmt-router-xyz" => "mgmt-router-xyz"

Terraform Configuration Files

resource "google_compute_router_peer" "gcp-xyz-rtr01-1" {
  provider		    = "google-beta"
  name                      = "gcp-xyz-rtr01-1"
  router                    = "mgmt-router-xyz"
  region                    = "asia-east1"
  peer_ip_address           = "169.254.163.11"
  peer_asn                  = 64526
  advertised_route_priority = 100
  interface                 = "${google_compute_router_interface.xyz-rtr01-1.name}"
}

### Panic Output

no panic

### Expected Behavior

Setting the proper variable to the resource should not force re-creation of the resource.

### Actual Behavior

Setting the proper variable to the resource force re-creation.

### Steps to Reproduce

Create a resource with an older version of the provider , move to the latest provider version apply config .

### Important Factoids

No

### References

<!---
Information about referencing Github Issues: https://help.github.com/articles/basic-writing-and-formatting-syntax/#referencing-issues-and-pull-requests

Are there any other GitHub issues (open or closed) or pull requests that should be linked here? Vendor documentation? For example:
--->

* #0000
@ghost ghost added the bug label Sep 18, 2019
@alterdinosu
Copy link
Author

turn out is not a bug

@ghost
Copy link

ghost commented Oct 18, 2019

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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks!

@ghost ghost locked and limited conversation to collaborators Oct 18, 2019
@github-actions github-actions bot added forward/review In review; remove label to forward service/compute-router labels Jan 15, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug forward/review In review; remove label to forward service/compute-router
Projects
None yet
Development

No branches or pull requests

1 participant