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.

Description

A new functionality for InternalRange is being added: a support of for-migration ranges. Such resources have the propetry usage=FOR_MIGRATION and they contain nested object consisting of 2 string: source - an URI/path to the migration source (a subnet resurce being migrated in its original location) and a target - an URI/path for the planned future resource (a subnet) to be recreated in the new location.

New or Affected Resource(s)

• google_network_connectivity_internal_range

Potential Terraform Configuration

resource "google_network_connectivity_internal_range" "migration" {
  name          = "migrate-subnet-from-source-to-target"
  description   = "a lock for subnet migration from source-subnet to planned-target-subnet"
  network       = google_compute_network.source-network.id
  ip_cidr_range = "10.100.1.0/24"
  peering       = "FOR_SELF"
  usage         = "FOR_MIGRATION"
  migration {
    source = google_compute_subnetwork.source-subnet.id
    target = "projects/${google_project.target-project.name}/regions/us-central1/subnetworks/planned-target-subnet"
  }
}

References

https://networkconnectivity.googleapis.com/$discovery/rest?version=v1