Consider moving this to equinix-labs

[displague]

Some guidance is available here: https://github.com/equinix-labs/equinix-labs/blob/main/terraform-modules.md#terraform-equinix-modules

Additional steps, specific to this repo:

• rename Packet to Equinix Metal (update any relevant links)
• should this module be 6.7 specific? (and/or 6.5 dependent)
  • replace 6.7 migration script with a 6.7 ESXi image?
• rename the project to terraform-metal-esxi-6-7
• update the resources from packet to metal
• update the variables and templates for TF 1+
• rename output.tf to outputs.tf
• rename templates/ to assets/
• perhaps: attach a network diagram to the README.md
• perhaps: replace output "Message" with a null resource provisioner that attempts to run a command after the reboot has started

[displague]

https://metal.equinix.com/developers/guides/vmware-esxi/

If you are looking for an automated way of doing this, we have a Terraform script that lets you deploy multiple servers with VMware ESXi 6.7 here.

"here" links to this project.

If this project is seen as a migration tool, the README.md should cover terraform import of existing resources before terraform apply.