google_vmwareengine_network_peering - Does not rebuild

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 a user, that user is claiming responsibility for the issue.
Customers working with a Google Technical Account Manager or Customer Engineer can ask them to reach out internally to expedite investigation and resolution of this issue.

Terraform Version

1.8.0

Affected Resource(s)

google_vmwareengine_network_peering

Terraform Configuration

Before:

resource "google_vmwareengine_network_peering" "ven-peering" {
  name                                = "ven-peering"
  vmware_engine_network               = google_vmwareengine_network.ven.id
  peer_network                        = "projects/prod/global/networks/vpc"
  peer_network_type                   = "STANDARD"
}

The requested change:

resource "google_vmwareengine_network_peering" "ven-peering" {
  name                                = "ven-peering"
  vmware_engine_network               = google_vmwareengine_network.ven.id
  peer_network                        = "projects/prod/global/networks/vpc"
  peer_network_type                   = "STANDARD"
  export_custom_routes                = false
  import_custom_routes                = true
  export_custom_routes_with_public_ip = true
  import_custom_routes_with_public_ip = false
}

Debug Output

# google_vmwareengine_network_peering.ven-peering will be updated in-place
  ~ resource "google_vmwareengine_network_peering" "ven-peering" {
      ~ export_custom_routes                = true -> false
        id                                  = "projects/prod/locations/global/networkPeerings/vpc"
      ~ import_custom_routes_with_public_ip = true -> false
        name                                = "ven-peering"
        # (11 unchanged attributes hidden)
    }

Expected Behavior

Based on the output above, terraform believes it can update in place. However, you cannot edit a vmware engine peering once it has been built. It should be destroying and rebuilding.

Actual Behavior

Nothing changes but terraform things it made the change.

Steps to reproduce

Build VMware engine peering
Try to change VMware engine peering

Important Factoids

No response

References