docs: Update references to docs.equinix.com (#956)

This updates references from the old deploy.equinix.com docs to the new
location and fixes links to VRFs that were incorrect.

Author: adammohammed

docs/data-sources/metal_device.md

@@ -64,7 +64,7 @@ output "ipv4" {
 - `plan` (String) The hardware config of the device
 - `ports` (List of Object) Ports assigned to the device (see [below for nested schema](#nestedatt--ports))
 - `root_password` (String, Sensitive) Root password to the server (if still available)
-- `sos_hostname` (String) The hostname to use for [Serial over SSH](https://deploy.equinix.com/developers/docs/metal/resilience-recovery/serial-over-ssh/) access to the device
+- `sos_hostname` (String) The hostname to use for [Serial over SSH](https://docs.equinix.com/metal/resilience-recovery/serial-over-ssh/) access to the device
 - `ssh_key_ids` (List of String) List of IDs of SSH keys deployed in the device, can be both user or project SSH keys
 - `state` (String) The state of the device
 - `storage` (String)

docs/data-sources/metal_gateway.md

@@ -6,7 +6,7 @@ subcategory: "Metal"
 
 Use this datasource to retrieve Metal Gateway resources in Equinix Metal.
 
-See the [Virtual Routing and Forwarding documentation](https://deploy.equinix.com/developers/docs/metal/layer2-networking/vrf/) for product details and API reference material.
+See the [Virtual Routing and Forwarding documentation](https://docs.equinix.com/metal/networking/vrf/) for product details and API reference material.
 
 ## Example Usage
 

docs/data-sources/metal_reserved_ip_block.md

@@ -8,7 +8,7 @@ Use this data source to find IP address blocks in Equinix Metal. You can use IP
 
 ~> For backward compatibility, this data source can be also used for precreated (management) IP blocks.
 
-See the [Virtual Routing and Forwarding documentation](https://deploy.equinix.com/developers/docs/metal/layer2-networking/vrf/) for product details and API reference material.
+See the [Virtual Routing and Forwarding documentation](https://docs.equinix.com/metal/networking/vrf/) for product details and API reference material.
 
 ## Example Usage
 

docs/data-sources/metal_virtual_circuit.md

@@ -4,9 +4,9 @@ subcategory: "Metal"
 
 # equinix_metal_virtual_circuit (Data Source)
 
-Use this data source to retrieve a virtual circuit resource from [Equinix Fabric - software-defined interconnections](https://deploy.equinix.com/developers/docs/metal/interconnections/introduction/)
+Use this data source to retrieve a virtual circuit resource from [Equinix Fabric - software-defined interconnections](https://docs.equinix.com/metal/interconnections/introduction/)
 
-See the [Virtual Routing and Forwarding documentation](https://deploy.equinix.com/developers/docs/metal/layer2-networking/vrf/) for product details and API reference material.
+See the [Virtual Routing and Forwarding documentation](https://docs.equinix.com/metal/networking/vrf/) for product details and API reference material.
 
 ## Example Usage
 
@@ -44,8 +44,8 @@ data "equinix_metal_virtual_circuit" "example_vc" {
 - `md5` (String, Sensitive) The password that can be set for the VRF BGP peer
 - `metal_ip` (String) The Metal IP address for the SVI (Switch Virtual Interface) of the VirtualCircuit. Will default to the first usable IP in the subnet.
 - `name` (String) Name of the virtual circuit
-- `nni_vlan` (Number) Nni VLAN parameter, see https://deploy.equinix.com/developers/docs/metal/interconnections/introduction/
-- `nni_vnid` (Number) Nni VLAN ID parameter, see https://deploy.equinix.com/developers/docs/metal/interconnections/introduction/
+- `nni_vlan` (Number) Nni VLAN parameter, see https://docs.equinix.com/metal/interconnections/introduction/
+- `nni_vnid` (Number) Nni VLAN ID parameter, see https://docs.equinix.com/metal/interconnections/introduction/
 - `peer_asn` (Number) The BGP ASN of the peer. The same ASN may be the used across several VCs, but it cannot be the same as the local_asn of the VRF.
 - `port_id` (String) UUID of the Connection Port where the VC is scoped to
 - `project_id` (String) ID of the projct to which the virtual circuit belongs
@@ -56,5 +56,5 @@ data "equinix_metal_virtual_circuit" "example_vc" {
 				 * For a /30 block, it will have four IP addresses, but the first and last IP addresses are not usable. We will default to the first usable IP address for the metal_ip.
 - `tags` (List of String) Tags attached to the virtual circuit
 - `vlan_id` (String) UUID of the associated VLAN
-- `vnid` (Number) VNID VLAN parameter, see https://deploy.equinix.com/developers/docs/metal/interconnections/introduction/
+- `vnid` (Number) VNID VLAN parameter, see https://docs.equinix.com/metal/interconnections/introduction/
 - `vrf_id` (String) UUID of the associated VRF

docs/data-sources/metal_vrf.md

@@ -6,7 +6,7 @@ subcategory: "Metal"
 
 Use this data source to retrieve a VRF resource.
 
-See the [Virtual Routing and Forwarding documentation](https://deploy.equinix.com/developers/docs/metal/layer2-networking/vrf/) for product details and API reference material.
+See the [Virtual Routing and Forwarding documentation](https://docs.equinix.com/metal/networking/vrf/) for product details and API reference material.
 
 ## Example Usage
 

docs/guides/migration_guide_facilities_to_metros_devices.md

@@ -4,7 +4,7 @@ page_title: "Migrating devices from facilities to metros"
 
 # Metros vs. Facilities
 
-In April 2021, [Equinix Metal](https://metal.equinix.com/) rolled out a new location concept - [metros](https://feedback.equinixmetal.com/changelog/new-metros-feature-live). A metro is an Equinix-wide concept for data centers which are grouped together geographically. Data centers within a metro share capacity and networking features. You can read more about metros at https://metal.equinix.com/developers/docs/locations/metros/. In April 2023, [facility deployment was deprecated](https://feedback.equinixmetal.com/changelog/bye-facilities-hello-again-metros) with metro provisioning offered as an all-around superior deployment strategy. See the [facilities guide in the Metal API docs](https://deploy.equinix.com/developers/docs/metal/locations/facilities/) for more details about the API change.
+In April 2021, [Equinix Metal](https://metal.equinix.com/) rolled out a new location concept - [metros](https://feedback.equinixmetal.com/changelog/new-metros-feature-live). A metro is an Equinix-wide concept for data centers which are grouped together geographically. Data centers within a metro share capacity and networking features. You can read more about metros at https://metal.equinix.com/developers/docs/locations/metros/. In April 2023, [facility deployment was deprecated](https://feedback.equinixmetal.com/changelog/bye-facilities-hello-again-metros) with metro provisioning offered as an all-around superior deployment strategy. See the [facilities guide in the Metal API docs](https://docs.equinix.com/metal/locations/facilities/) for more details about the API change.
 
 Before the introduction of metros, resources were deployed to a single `facility` location.  When provisioning `equinix_metal_device` resources, the facility could be chosen by Equinix Metal with a user-supplied list of `facilities`, or a wildcard `any` facility.  The individual facility locations use a code like "sv15" or "ny5". Metros group facilities. For example, metro "sv" contains the "sv15" facility, among others. If you specify a metro when creating a resource, it will be deployed to one of the facilities in the metro group. You can then find the deployed facility using a read-only attribute of the resource (e.g. `deployed_facility` for `equinix_metal_device` resources).
 

docs/guides/network_types.md

@@ -7,7 +7,7 @@ page_title: "Metal Device Network Types"
 
 Server network types, such as Layer-2, Layer-3, and Hybrid may be familiar to users of the Equinix Metal Portal. In the Portal, you can toggle the network type with a click of the UI. To take advantage of these features in Terraform, which closely follows the Equinix Metal API, it is important to understand that the network type is a composite string value determined by one or more port bonding, addressing, and VLAN attachment configurations. To change the network type, you must change these underlying properties of the port(s).
 
-For more details, see the Equinix Metal documentation on [Network Configuration Types](https://metal.equinix.com/developers/docs/layer2-networking/overview/#network-configuration-types).
+For more details, see the Equinix Metal documentation on [Network Configuration Types](https://docs.equinix.com/metal/layer2-networking/overview#network-configuration-types).
 
 This Terraform provider offers two ways to define the network type.
 
@@ -38,7 +38,7 @@ resource "equinix_metal_port" "eth1" {
 
 ### Layer 2 Unbonded Port
 
-This example configures an Equinix Metal server with a [pure layer 2 unbonded](https://deploy.equinix.com/developers/docs/metal/layer2-networking/layer2-mode/#:~:text=Layer%202%20Unbonded%20Mode) network configuration and adds two VLANs to its `eth1` port; one of them set as the [native VLAN](https://deploy.equinix.com/developers/docs/metal/layer2-networking/native-vlan/). Notice the `depends_on` meta-argument in the `equinix_metal_port.eth1` resource and the `reset_on_delete` attribute in both ports’ configuration. The `reset_on_delete` will set the port to the default settings (layer3 bonded without VLANs attached) before the terraform resource delete/destroy. It is recommended to use the `depends_on` argument here to ensure that the port resources with attached VLANs are reset first, since all VLANs must be detached before re-bonding the ports.
+This example configures an Equinix Metal server with a [pure layer 2 unbonded](https://docs.equinix.com/metal/layer2-networking/layer2-mode/#:~:text=Layer%202%20Unbonded%20Mode) network configuration and adds two VLANs to its `eth1` port; one of them set as the [native VLAN](https://docs.equinix.com/metal/layer2-networking/native-vlan/). Notice the `depends_on` meta-argument in the `equinix_metal_port.eth1` resource and the `reset_on_delete` attribute in both ports’ configuration. The `reset_on_delete` will set the port to the default settings (layer3 bonded without VLANs attached) before the terraform resource delete/destroy. It is recommended to use the `depends_on` argument here to ensure that the port resources with attached VLANs are reset first, since all VLANs must be detached before re-bonding the ports.
 
 ```hcl
 resource "equinix_metal_port" "bond0" {

docs/resources/metal_device.md

@@ -155,7 +155,7 @@ resource "equinix_metal_device" "pxe1" {
 ### Required
 
 - `operating_system` (String) The operating system slug. To find the slug, or visit [Operating Systems API docs](https://metal.equinix.com/developers/api/operatingsystems), set your API auth token in the top of the page and see JSON from the API response.  By default, changing this attribute will cause your device to be deleted and recreated.  If `reinstall` is enabled, the device will be updated in-place instead of recreated.
-- `plan` (String) The device plan slug. To find the plan slug, visit the [bare-metal server](https://deploy.equinix.com/product/bare-metal/servers/) and [plan documentation](https://deploy.equinix.com/developers/docs/metal/hardware/standard-servers/)
+- `plan` (String) The device plan slug. To find the plan slug, visit the [plan documentation](https://docs.equinix.com/metal/hardware/standard-servers/)
 - `project_id` (String) The ID of the project in which to create the device
 
 ### Optional
@@ -196,7 +196,7 @@ resource "equinix_metal_device" "pxe1" {
 - `network_type` (String, Deprecated) Network type of a device, used in [Layer 2 networking](https://metal.equinix.com/developers/docs/networking/layer2/). Will be one of layer3, hybrid, hybrid-bonded, layer2-individual, layer2-bonded
 - `ports` (List of Object) Ports assigned to the device (see [below for nested schema](#nestedatt--ports))
 - `root_password` (String, Sensitive) Root password to the server (disabled after 24 hours)
-- `sos_hostname` (String) The hostname to use for [Serial over SSH](https://deploy.equinix.com/developers/docs/metal/resilience-recovery/serial-over-ssh/) access to the device
+- `sos_hostname` (String) The hostname to use for [Serial over SSH](https://docs.equinix.com/metal/resilience-recovery/serial-over-ssh/) access to the device
 - `ssh_key_ids` (List of String) List of IDs of SSH keys deployed in the device, can be both user and project SSH keys
 - `state` (String) The status of the device
 - `updated` (String) The timestamp for the last time the device was updated

docs/resources/metal_gateway.md

@@ -6,7 +6,7 @@ subcategory: "Metal"
 
 Use this resource to create Metal Gateway resources in Equinix Metal.
 
-See the [Virtual Routing and Forwarding documentation](https://deploy.equinix.com/developers/docs/metal/layer2-networking/vrf/) for product details and API reference material.
+See the [Virtual Routing and Forwarding documentation](https://docs.equinix.com/metal/networking/vrf/) for product details and API reference material.
 
 ## Example Usage
 

docs/resources/metal_reserved_ip_block.md

@@ -14,7 +14,7 @@ Addresses from global blocks can be assigned in any metro. Global blocks can hav
 
 Once IP block is allocated or imported, an address from it can be assigned to device with the `equinix_metal_ip_attachment` resource.
 
-See the [Virtual Routing and Forwarding documentation](https://deploy.equinix.com/developers/docs/metal/layer2-networking/vrf/) for product details and API reference material.
+See the [Virtual Routing and Forwarding documentation](https://docs.equinix.com/metal/networking/vrf/) for product details and API reference material.
 
 ## Example Usage